Hi Misagh, Thanks for the quick reply. I had played with option 1 but the resolvers in the MergingPersonAttributeDaoImpl are converted into an unmodifiable list when they are first set. That being said, the groovy option does look promising for what we need.
Thanks, Adam On Monday, June 26, 2017 at 3:41:23 PM UTC-4, Misagh Moayyed wrote: > > Yes. You essentially do what that component does: > > > > 1. Write a configuration object that receives the prebuilt > collection of repositories as an autowired field, insert yours into it. > > 2. Submit a pull request to Github, building support for custom > resolvers in a “sane” way. Then simply consume the feature in your overlay > and configure it as you see fit. > > > > Or do the Groovy option and retrieve anything you like. > > > > --Misagh > > > > *From:* [email protected] <javascript:> [mailto:[email protected] > <javascript:>] *On Behalf Of *Adam Young > *Sent:* Monday, June 26, 2017 12:24 PM > *To:* CAS Community <[email protected] <javascript:>> > *Subject:* [cas-user] CAS 5.0.5: Mixing default and custom attribute > resolvers (PersonAttributeDao) > > > > 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] <javascript:>. > 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 > > <https://groups.google.com/a/apereo.org/d/msgid/cas-user/af669ef3-72fb-4d00-8d90-32a355fbd84e%40apereo.org?utm_medium=email&utm_source=footer> > . > -- - 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/48317bd5-1316-46fb-8fdc-77a983a92e46%40apereo.org.
