Hello, We upgraded our CAS server from 3.5.2 to 4.2.6 and we observe a difference in the way the principal username is returned to CASsified app.
Before, I think that CAS returned the username as it was typed in the login form by the user. But now, CAS returns the username (SAMAccountName in our case) as it has been created in our directory. For some reasons, our SAMAccountName are mixed cased, and the applications which don’t force the case on the username they get from CAS, don’t do the matching between the username and their user table. Is there a way to lower case the username as it will be sent to applications ? I’ve found PrincipalNameTransformer but it’s between the username typed in the form and the authenticationHandler. GroovyPersonAttributeDao could be a way to this ? Have you got some documentation about it ? Thank you -- - CAS gitter chatroom: https://gitter.im/apereo/cas - CAS mailing list guidelines: https://apereo.github.io/cas/Mailing-Lists.html - CAS documentation website: https://apereo.github.io/cas - CAS project website: https://github.com/apereo/cas --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/6475C67F-5989-41F1-81CE-6889AD6D3E4A%40univ-lyon1.fr.
smime.p7s
Description: S/MIME cryptographic signature
