Barry Silk wrote: > The solution I've come up with does not involve CAS: change the "uid" > object's m-equality attribute in the LDAP schema from > "caseIgnoreMatch" to "caseExactMatch" -- this produces the desired > case-sensitive authentication.
Note that exactly this is bad practice since the standard defines 'uid' with case-insensitive matching. So this schema change has to be applied each time you update your server and might break other apps. I'd strongly recommend to rethink your requirement for case-sensitive userid or at least define a custom attribute. Ciao, Michael. -- 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
