Transport-level protection of JAX-RS endpoints can be managed by underlying Servlet containers, for example, see this Tomcat SSL Configuration section.
Additionally CXF provides support for configuring endpoints which depend on embedded Jetty. CXF JAX-RS clients can also be configured to support SSL.
JAX-RS endpoints using embedded Jetty can rely on the configuration like this one:
Instead keyPassword in keyManager you can also specify keyPasswordCallbackHandler attribute. In this case attribute must contain full name of the class implementing JSE CallbackHandler interface and providing key password on the runtime. Sample key password callback handler implementation can be found here.
If you use JAXRSServerFactoryBean to create and start JAX-RS endpoints from the code then the above configuration can be utilized like this:
If you also have a jaxrs:server endpoint declared in the above beans.xml, then make sure you have a 'depends-on' attribute set:
Once you have JAX-RS and Jetty HTTPS combined then you can get the application context initiated like this:
Having JAX-RS endpoints declared alongside CXF Jetty HTTPS configuration is only needed when an embedded Jetty container is used. If you have application WARs deployed into Tomcat or Jetty then please follow container-specific guides on how to set up SSL.
Please also see this HTTPS-based demo in the CXF distribution.
Additionally check the CXF Jetty Configuration section.
Secure HTTPConduits for CXF JAX-RS proxies and WebClients can be configured as described in this section.
For example, check this configuration file. Endpoint addresses used by proxies or clients have to match the pattern used in the HTTPConduit configuration.
The configuration file can be referenced during the proxy or WebClient creation:
HTTPConduits can also be 'bound' to proxies or WebClients using expanded QNames. Please see this section for more information.
Please see this blog entry on how the HTTPConduit TLS properties can be set up from the code. In the code, do WebClient.getConfig(myClient).getHTTPConduit() and proceed from there.
It is often containers like Tomcat or frameworks like Spring Security which handle the user authentication. Sometimes you might want to do the custom authentication instead. CXF HTTP Transport adds decoded Basic Authentication credentials into an instance of AuthorizationPolicy extension and sets it on the current message. Thus the easiest way is to register a custom invoker or
RequestHandler filter which will extract a user name and password like this:
One other thing you may want to do, after authenticating a user, is to initialize org.apache.cxf.security.SecurityContext with Principals representing the user and its roles (if available).
If you prefer using Spring Security then see how the authentication is handled in a spring-security demo.
Next, please see the Security section on how CXF Security interceptors can help.
Additionally check this blog entry for more information on how CXF JAX-RS wraps the CXF security interceptors with helper filters.
For example, see how a JAX-RS filter can be used to wrap CXF JAASLoginInterceptor:
The filter will redirect the client to "/login.jsp" if the authentication fails. If no 'redirectURI' property is set then 401 will be returned. A "realmName" property can also be set.
If the JAAS Authentication succeeds then the filter will set a SecurityContext instance on the message. This context can be used for authorization decisions.
It is often containers like Tomcat or frameworks like Spring Security which handle user authorization, similarly to the way the authentication is handled.
CXF also provides two interceptors which make it easy to enforce authorization decisions, as described in the Security section.
CXF JAX-RS SimpleAuthorizingFilter can be used to wrap those interceptors and return 403 in case of failures:
SimpleAuthorizingFilter can also wrap CXF SecureAnnotationsInterceptor.
Note that wrapping CXF security interceptors with JAX-RS filters is not required; it simply makes it easier to handle authentication and authorization exceptions and return appropriate HTTP error statuses.
One of the requirements for deploying CXF endpoints into secure web service environments is to ensure that existing WS-Trust STS services can be used to protect the endpoints. JAX-WS endpoints can rely on CXF WS-Security and WS-Trust support. Making sure CXF JAX-RS endpoints can be additionally secured by STS is strategically important task. CXF provides close integration between JAX-WS and JAX-RS frontends thus reusing CXF JAX-WS and WS-Security is the most effective way toward achieving this integration.
Validating Basic Authentication credentials with STS is possible starting from CXF 2.4.1. JAX-RS and JAX-WS services can rely on this feature. Here is an example on how a jaxrs endpoint can be configured:
AuthPolicyValidatingInterceptor converts Basic Auth info into WSS4J UsernameToken and delegates to STS to validate.
Please see this section for more information on how STSTokenValidator can be used to validate the inbound SAML assertions.
java.lang.SecurityManager is installed then you'll likely need to configure the trusted JAX-RS codebase with a 'suppressAccessChecks' permission for the injection of JAXRS context or parameter fields to succeed. For example, you may want to update a Tomcat catalina.policy with the following permission :
Please check JAX-RS XML Security, JAX-RS SAML and JAX-RS OAuth2 pages for more information about the advanced security topics.
Please see this section for more information.
Please see this section for more information. Also check the section about JSONP.