We are currently using the default attribute resolvers for LDAP and jdbc with no issues. We configure them via the properties file and everything works as expected.
We have now been given new requirements that will involve us having to write a custom implementation of IPersonAttributeDao to resolve additional attributes that the LDAP and jdbc sources know nothing about. Our problem is that I cannot figure out how to configure this attribute resolver to be used in conjunction with the other default resolvers. Looking at the source it seems that CasPersonDirectoryAttributeRepositoryConfiguration is creating the attributeRepository bean by adding all of the default configured attribute resolvers into a MergingPersonAttributeDaoImpl. This is fine but the list of possible resolvers that can be added seems to be hard coded in that class. We would like to continue to use the default resolvers with their simple configuration but have our own customer resolver added to the set of resolvers that are used. Is there a supported way of configuring this that I'm missing? Thanks, Adam -- - 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/af669ef3-72fb-4d00-8d90-32a355fbd84e%40apereo.org.
