Hi, I am trying to use an LDAP attribute with options named "supannCMSId;x-desfire-xmsb" with the attributes resolver. It causes some troubles with legacy applications, probably because of some parsing issues due to the semicolon. For now, I have no control on the datasource so I have to use the datas "as is" . My main workaround is to try mapping it on some "regular" attribute alias. So far, I have tried this syntax, with a backslash quoting the semicolon and without : cas.authn.attribute-repository.ldap[0].attributes.supannCMSId;x-desfire-xmsb=supannCMSId The source attribute is resolved of course, but "supannCMSId" is not valued. I also runned an dumb test, using : cas.authn.attribute-repository.ldap[0].attributes.mail=mail,supannCMSId It's works. I also tried this in an OIDC context, and this line gives the expected result: cas.authn.oidc.core.claims-map.supanncmsid=supannCMSId;x-desfire-xmsb So I guess it's a syntax problem, having the semicolon on key, and I have no idea how to write things. Thanks for any kind of help. Regards
------------------------------------------------------------------------------------------------- FreeMail powered by mail.fr -- - Website: https://apereo.github.io/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 visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/f1d0e4af91a333acafce8703790690f35061780c%40mail.de.
