Hello,
I'm implementing CAS 6.6.x (currently I have 6.6.8), and I need to make an association between authentication handlers and attribute repositories / PersonAttributeDaos, for example, LdapAuthHandler[0] => Dao1, Dao2 and JdbcAuthHandler[0] => Dao1, Dao3. The goal is that each auth handler only tries to get attributes from the attribute repositories that make sense to it. I'm trying to do this, by creating a custom property in cas.properties for each auth handler, that holds a comma-separated list of one or more attribute repositories Ids (defined in standard props "cas.authn.attribute-repository.<ldap/jdbc/etc>.id"). I got this ideia from the standard property "cas.person-directory.active-attribute-repository-ids". Then, my plan is to extend the PersonDirectoryPrincipalResolver and manipulate the context.attributeRepository.personAttributeDaos, so that only the Daos that the auth handler "supports" are "executed". Does this makes sense? Is it a possible and logic solution? Is there a better "standard solution" ? Best regards, Luís Costa -- - 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/ae3bd322-0b0d-41ea-a157-8f894071f72dn%40apereo.org.
