Aaron, Do you have the attribute repository defined with: cas.authn.attribute-repository. ... properties?
Ray On Wed, 2023-08-30 at 13:04 -0700, Aaron Chantrill wrote: Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. I'm trying to use a specific attribute repository after authenticating with Azure AD as a delegate identity provider. Authenticating with Azure AD works fine and I can see the attributes, but really I just want to use the samaccountname attribute to retrieve attributes from a database. Previously I had both LDAP and JDBC identity providers (for different types of users) and both of them used the only attribute repository I had defined, but it seems like delegate identity providers like to use their own attributes. Is there some way to force CAS to append attributes from a different attribute provider after authenticating with a delegate identity provider? 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 cas-user+unsubscr...@apereo.org. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/2c2e17b899751fc1c56cff4b0962e8107929eee0.camel%40uvic.ca.
