Mike Youngstrom wrote:
Maybe I'm missing something but it appears that the only CAS and
AuthenticationDao integration point is in the DaoCasAuthoritiesPopulator
in "getAuthorities" method where it appears to only load the user in
order to get the authorities().
Maybe I should ask my question this w
Patrick Burleson wrote:
It would appear to me that the Authentication isn't Serializable and
thus gets rejected from my session on Weblogic (well, I get a warning
that it will be upon redeployment). Is this intentional?
Hi Patrick
I've just made Authentication Serializable in CVS HEAD.
Best rega
It would appear to me that the Authentication isn't Serializable and
thus gets rejected from my session on Weblogic (well, I get a warning
that it will be upon redeployment). Is this intentional?
Thanks,
Patrick
---
This SF.Net email sponsored
Ben,
Thanks for the reply.
>Just customise your AuthenticationDao's loadUserByUsername method, and
the Authentication token generated
>by the CAS packages should contain your custom UserDetails.
Maybe I'm missing something but it appears that the only CAS and
AuthenticationDao integration point
Ben,
Thanks for the reply.
>Just customise your AuthenticationDao's loadUserByUsername method, and
>the Authentication token generated by the CAS packages should contain
>your custom UserDetails.
Maybe I'm missing something but it appears that the only CAS and
AuthenticationDao integration poi
