-
Bug
-
Resolution: Done
-
Major
-
3.0.16.Final
-
None
RESTEASY-1249 introduced default message for 403 errors generated by RoleBasedSecurityFilter. However, this default message cannot be overridden by an ExceptionMapper, because an ExceptionMapper is not executed on exceptions that already have an entity. This makes it impossible to customize the response body (or headers) for those errors, and is essentially a regression.
Workaround: ContainerResponseFilter can still be used to customize response, but it would have to filter all responses by status and at that point exception info is already partially lost.
- is caused by
-
RESTEASY-1249 If RoleBased authorization fails the response returned doesn't contain a body text
- Closed
- is cloned by
-
JBEAP-7984 RoleBasedSecurityFilter doesn't allow customizing response
- Closed
- is related to
-
RESTEASY-1067 Throwing WebApplicationException standard subclasses doesn't produce correct error message
- Closed
-
RESTEASY-1252 Resteasy logs Error stacktrace after every unauthorized request
- Closed
- relates to
-
RESTEASY-1563 RoleBasedSecurityFilter doesn't alter the Content-Type header
- Resolved