Andy Depue wrote:
I solved my problem by not using encoded passwords - now everything is working as expected... this will work during development, but won't be an option when we deploy. It appears that my version of Acegi has a bug concerning encoded passwords (see my previous post for details).
Hi Andy
Well done for picking that one up - the fix is in CVS.
I have also added the stack trace logging to SecurityEnforcementFilter as suggested.
Did you still need some feedback on your AuthenticationProcessingFilter email, or did you sort that one out? The current CVS HEAD contains some enhancements that assist with processing additional authentication information, so you might like to see if that helps. The thread, "Customizing DaoAuthenticationProvider, et al", talks a little more about it.
Best regards Ben
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Acegisecurity-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
