I'm trying to get Spring Security 3.0 working with a Struts 2.0.18 web-app
that uses the Convention plugin using a customised login form. So far I've
got
<form-login login-page="/login" default-target-url="/startup"
always-use-default-target="false"
authentication-failure-url="/login?authfailed=true"
/>
<access-denied-handler error-page="/login?notauthorized=true"/>
<logout />
"login" and "startup" are Struts actions and work fine for the login-page,
default-target-url and authentication-failure-url tags, but when called
through the access-denied-handler I get an Apache-Tomcat 404 error - so it's
not even making it into Struts! This is an error that I particularly want to
catch and log.
Has anyone managed to get the access-denied-handler to cope with a Struts
action?
Regards
--
View this message in context:
http://old.nabble.com/Struts---Spring-Security-tp28409361p28409361.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
