I'll double check but I'm pretty sure that's a bug. If so I'll get it
committed either tonight or tomorrow. US time that is :P
-Ray
On 7/21/05, Tim Kettering <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> I was tracking down some issues that came up after we started using our own
> UserDetails object in the principal of Authentication. This method in
> JaasNameCallbackHandler seems to be calling the incorrect method. In
> AbstractAuthenticationHandler, the methods called are
> 'authentication.getPrincipal().getUsername()' not
> 'toString()' like it appears below. Is there any reason for this? The
> problem we are facing is that our JAAS handler is trying to authenticate on
> the entire toString() output of our UserDetails object, instead of just the
> username, at this point, when the Acegi API/source seems to indicate that
> toString() is to be used for debug output.
>
>
>
> public void handle(Callback callback, Authentication authentication)
>
> throws IOException, UnsupportedCallbackException {
>
> if (callback instanceof NameCallback) {
>
> NameCallback ncb = (NameCallback) callback;
>
> ncb.setName(authentication.getPrincipal().toString());
>
> }
>
> }
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Home: http://acegisecurity.sourceforge.net
Acegisecurity-developer mailing list
Acegisecurity-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
