If you wanted to you could store some information in a custom UsernamePasswordCredentials that has additional fields (we do it for certain scenarios).  You could also do the look up again depending on how expensive it is (if you use connection pooling the look up expense may be minimal).

-Scott

On 10/3/06, Jennifer Yang <[EMAIL PROTECTED]> wrote:
Scott,

That's great.  I can plug in our own.

One more question.  Our auth backend function actually returns a bunch of things, including principal.   Is there any way we can store the returned principal to be used by the CredentialsToPrincipalResolver so that we don't have to do the same lookup in both AuthenticationHandler and CredentialsToPrincipalResolver ?

--Jennifer

_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev



_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev

Reply via email to