Daniel Woo(Migrated from SEC-1100) said:
Currently security:http does not allow replacing the AccessDeniedHandler in exceptionTranslationFilter, need to add an attribute reference to the desired AccessDeniedHandler.
Ryan Holliday said:
This functionality would also be helpful with the JAMWiki project’s Spring Security implementation. Currently the project uses a single user database but has the concept of “virtual” instances such as “/context/instance1/” and “/context/instance2” to simplify management. The different “instances” are primarily used for determining what language to display a page in, but there is additional functionality that makes having separate instances important. With current Spring Security namespace configuation we could specify an “access-denied-page” reference on the http attribute, but that would force all access denied errors to a single page, and we actually need to make sure that users are sent to the appropriate sub-page for whatever “instance” they are on.
Luke Taylor said:
I've added support for an element, which should be used in preference to the original access-denied-page attribute.
It can take either a reference or an "error-page" attribute: