No, I don't want to change that behavior for now. Lots of custom coding ahead.. wow. I don't like where I am heading, but I need to do it. For example, there exists org.jasig.cas.util.LdapUtils, but not org.jasig.cas.util.JdbcUtils.. so there I go. And ditto for AbstractJdbcPersonDirectoryCredentialsToPrincipalResolver, which does not exit, usw. I welcome myself to the open source :) Thanks Marvin, for the comments.
--- On Thu, 2012/2/9, Marvin Addison <[email protected]> wrote: > Now, how is it decided that a particular request should use (1) or (2) above? By default the first resolver that supports a given credential type is used. You can change that behavior by using an alternative authentication manager such as org.jasig.cas.authentication.DirectMappingAuthenticationManagerImpl. I would not be surprised if you needed to develop a custom AuthenticationManager component to suit your needs. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
