With CAS 3.3.5 it appears that when adding leading and/or trailing backslashes creates some interesting behavior.
Say the user enters "\bob\" instead of his normal login "bob". The user "\bob\" does not exist in the systems we are binding against, while "bob" does. When CAS binds against SunOne LDAP the slashes are dropped somewhere along the way and the user "bob" is authenticated. The issue that arises is that the username "\bob\" is then passed on by CAS as the validated username, which is incorrect. Any suggestions on where to correctly adjust for this? My searching has found one ancient bug regarding the dropping of needed slashes, but nothing pertaining to this particular issue. Raymond Walker Software Systems Engineer Sr. ITS Northern Arizona University -- 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-user
