You can let you handler retrieve every attribute via the configuration, and define a separate attribute repository for the management app that is LDAP-based. Remember that, that only controls what attributes are released, not what is retrieved.
- Misagh > On Dec 1, 2015, at 5:13 PM, Matt S. <[email protected]> wrote: > > Hello, > > I've been working on setting up CAS server 4.1.2 and the Management webapp > and have gotten both deployed successfully for testing, with authentication > being done via an LdapAuthenticationHandler. > > Based on the documentation for setting up Ldap, it lets you specify the > attributes directly in the authentication handler. > However, I've noticed that when accessing the Management webapp, it currently > does not list the same attributes that I specified in the Server > deployerConfigContext, which makes sense since the Management webapp is now > separate. > > Is there any way to have the Management webapp see / use the same list of > attributes already specified in the Server without manually listing them > again in the managementConfigContext.xml for the Management webapp and > therefore having to maintain the list in both the Server and the Management > webapps? > > > Thanks, > Matt > > -- > 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] > <mailto:[email protected]>. > Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/ > <http://groups.google.com/a/apereo.org/group/cas-user/>. -- 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]. Visit this group at http://groups.google.com/a/apereo.org/group/cas-user/.
