Yes, please identify any issues/use cases/requirements/etc. with the existing set ups. CAS4 will give us a chance to make things easier/correct stuff!
I've already re-worked the PasswordEncoder support to actually be useful ;-) -Scott -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia On Wed, Dec 17, 2008 at 4:00 PM, Marvin S. Addison <marvin.addi...@gmail.com > wrote: > You should not have to modify SamlAuthenticationMetaDataPopulator, > provided each of your authentication methods maps to a distinct+ > credentials class. If that is the case, you can simply set the > userDefinedMappings property on that class with how your credentials > classes should map to SAML authentication method URNs. > > Dealing with different URNs for the _same_ credentials class is another > matter. In our case we have two distinct types of principals that > authenticate via LDAP, a level 2 user and a level 1 user (in NIST 800-63 > parlance). Both of these are UsernamePasswordCredentials cases, so we'd > need to provide a different implementation of > AuthenticationMetaDataPopulator to handle this case. > > I wonder if others have use cases like ours above. Please speak up if > that is the case. > > Thanks, > Marvin > > _______________________________________________ > cas-dev mailing list > cas-dev@tp.its.yale.edu > http://tp.its.yale.edu/mailman/listinfo/cas-dev >
_______________________________________________ cas-dev mailing list cas-dev@tp.its.yale.edu http://tp.its.yale.edu/mailman/listinfo/cas-dev
