I\'m trying to use a ContainerRequestFilter
to enforce some authentication on a Tomcat based Jersey application. I followed this document.
Problem : the filter
Some hints:
Make sure you're using the right imports in your filter:
import javax.ws.rs.container.ContainerRequestContext;
import javax.ws.rs.container.ContainerRequestFilter;
Add the @Provider
annotation
Instead of using the @Provider
annotation (which did not work in my case), you can register your ContainerRequestFilter
manually with your JerseyServletFactory
:
JerseyServletFactory jerseyServletFactory = new JerseyServletFactory(config);
HttpServlet myServiceServlet = jerseyServletFactory.create(myResource);
// Register your ContainerRequestFilter like this
jerseyServletFactory.addRequestFilter(new MyFilter());
httpServer.register(myServiceServlet, "/api");
httpServer.start();
If you were stuck like me, note that TomEE 1.7.X uses JAX-RS 1.1, which does not include ContainerRequestFilter.
Instead of javax.ws.rs, i used com.sun.jersey and it worked
import com.sun.jersey.spi.container.ContainerRequestFilter
import com.sun.jersey.spi.container.ContainerRequest
Dropwizard users need to do this
environment.jersey().getResourceConfig()
.getContainerRequestFilters()
.add(filter);
Okay, I didn't get that the jersey.config.server.provider.packages
init param needs to reference not only service classes (API endpoints) but ALL the classes including filters.
Now it works :
<init-param>
<param-name>jersey.config.server.provider.packages</param-name>
<param-value>com.hck.debate.rest.controller;com.hck.debate.rest.security</param-value>
</init-param>
<init-param>
<param-name>com.sun.jersey.spi.container.ContainerRequestFilters</param-name>
<param-value>com.hck.debate.rest.security.AuthFilter</param-value>
</init-param>
The minimum requirements to work filters with jersey:
Any other settings aren't required (e.g. 'com.sun.jersey.spi.container.ContainerRequestFilters' init-param or ResourceConfig)