> I have been searching the forums and documentation to see if there are any > prohibited characters.
There's no inherent limit imposed by CAS on allowed characters. > I did find issues with a user entering a special > character, such as a ',' without UTF-8 encoding. CAS ships with UTF-8 encoding by default, so you shouldn't have to explicitly handle UTF-8 encoding. It's possible you have custom configuration that's overriding the default behavior. See https://wiki.jasig.org/display/CASUM/Internationalization for more information. > Does CAS enforce a '\' for the character in transmission to the LDAP server > per RFC 4515? In debugging statements, the clear text string shows no such > translation. LDAP protocol encoding happens in the Sun/Oracle JNDI components. I don't have any evidence that that particular case is covered, but based on experience with other JNDI parts I'm fairly certain all encoding is performed correctly. Sun tends to be very strict in protocol compliance generally, and JNDI is no exception in my experience. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
