at the json
service:
https://apereo.github.io/cas/5.1.x/integration/Attribute-Release-PrincipalId.html
"usernameAttributeProvider": {
"@class": "org.apereo.cas.services.DefaultRegisteredServiceUsernameProvider",
"canonicalizationMode": "LOWER",
"encryptUsername": false
},
El miércoles, 2 de noviembre de 2016, 11:43:19 (UTC+1), HURTEVENT VINCENT
escribió:
>
> 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
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
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/07e9600f-c2e7-447a-aa0c-d51366b7869f%40apereo.org.
