Ofc I did triple checked everything that's in the doc of 4.2.x.
No errors in the log. The logging is on debug, this is how I found out, that the problem was not having a credential attribute released. After that I set up the StubPersonAttributeDao again, mapped an arbitrary string value for the credential attribute, and all that is described in the doc like the encryption was working, except the fact that the released credential attribute was a static value instead of the given principal's credential. So you say that even if I have the StubPersonAttributeDao like in the default overlay and the authorizedToReleaseCredentialPassword set to true for the used service, it should automatically release the credential attribute? No further dependency (like clearpass) or configuration needed like the ones the 4.0.x doc describes? Could you provide me (and the community:) a deployerConfigContext.xml that is releasing the authenticated users credential? Tomorrow I can also send you the logs just to be sure I didn't miss anything. Many thanks! -- 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 cas-user+unsubscr...@apereo.org. To post to this group, send email to cas-user@apereo.org. Visit this group at https://groups.google.com/a/apereo.org/group/cas-user/. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/418184cf-6c5b-49a5-afad-d0f557b9971f%40apereo.org. For more options, visit https://groups.google.com/a/apereo.org/d/optout.
