I'm a newbie to acegi-security and am running into a problem (probably
something stupid on my end). Anyway, I have a page that is protected. The
definition in my FilterSecurityInterceptor goes something like this:
/rcp/launchhr.jsp=ROLE_HUMANRESOURCES
Ok, so I attempt to access the page and a
One of the things that could help me diagnose this problem is if
SecurityEnforcementFilter would log a stack trace of AuthenticationException
when it catches it (see Acegi v 0.51 SecurityEnforcementFilter.java line
170). Right now, the source exception is completely discarded - making it
diffi
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).
--
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)
Yeah, I've gotten around the issue for now by using redirect - but will need
to look at it again soon. I'll see if CVS HEAD provides more functionality.
Basically, our app provides different "user spaces". When a user logs in,
they must provide both a user space and a username (usernames need
