Rob Moore wrote:
I think a bug has been introduced in the 0.8.1 enhancement to User.toString(). Previously, calling SecureContext.getAuthentication().getName() returned the usernname. Now it seems to return the result of User.toString().
Here's an example of what I'm seeing on the getName() call:
[EMAIL PROTECTED]: Username: myUser; Password: [PROTECTED]; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: ROLE_IT_ADMINISTRATOR, ROLE_PURCHASING_MANAGER, ROLE_ACCOUNTING, ROLE_PRICING_MANAGER, ROLE_PURCHASING_CLERK, ROLE_USER, ROLE_OPERATIONS_MANAGER, ROLE_PRICING_CLERK, ROLE_OWNER_OPERATOR ***************
Whereas previously I would have gotten back simply 'myUser'.
Regards,
Rob
Hi Rob
I did consider this, but I felt users wanting a username would have been using User.getUsername(). I personally use .toString() for debugging, and find the extra details helpful. Any concerns with swapping to getUsername()?
Cheers Ben
------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ Home: http://acegisecurity.sourceforge.net Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
