CAS 4.2.0 RC1:
Which is the preferred way now to configure the AuthenticationHandler
stack for 4.2 and beyond?
This one looks to be wired into AbstractAuthenticationManager.
> <util:map id="authenticationHandlersResolvers">
> <entry key-ref="proxyAuthenticationHandler"
> value-ref="proxyPrincipalResolver" />
> <entry key-ref="primaryAuthenticationHandler"
> value-ref="primaryPrincipalResolver" />
> </util:map>
setting primaryPrincipalResolver to "#{null}" when appropriate.
Then I see e.g.
> <bean id="authenticationManager"
> class="org.jasig.cas.authentication.PolicyBasedAuthenticationManager">
> <constructor-arg>
> <map>
> <entry key-ref="acceptUsersAuthenticationHandler"
> value-ref="usernamePasswordCredentialsResolver" />
> <entry key-ref="x509AuthenticationHandler"
> value-ref="x509CredentialsResolver" />
> <entry key-ref="httpBasedAuthenticationHandler"
> value-ref="httpBasedCredentialsResolver" />
> </map>
> </constructor-arg>
> </bean>
This class extends AbstractAuthenticationManager.
Most configuration files in the distribution seem to use the first
syntax. I'd guess either could work, though.
Thanks.
Tom.
--
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 https://groups.google.com/a/apereo.org/group/cas-user/.
