Liberty profile: Implementation of secure JAX-RS applications

The JAX-RS runtime environment from IBM® is driven by a servlet derived from the Apache Wink project. Within the WebSphere® Application Server environment, the lifecycle of servlets is managed in the web container. Therefore, the security services offered by the web container are applicable to REST resources that are deployed in WebSphere Application Server.

You can define and add security constraints on the REST resources using the same tooling that is used to assemble REST applications. These constraints are captured in the J2EE web deployment descriptor that is associated with your application. The following list describes security definitions that you can include in the deployment descriptor:
  • User authentication when invoking REST resources embodied in the application, including
    • HTTP basic authentication.
    • Form login authentication.
  • Authorization control over REST resources as defined by the URL patterns for the resources.
  • Use of SSL for transport when invoking REST resources.
  • Programmatic use of the SecurityContext object to determine user identity and roles.
All the security mechanisms supported by the web container are applicable to REST resources, including the use of the Kerberos-based SPNEGO authentication mechanism.
For more information, see:
Note: In the Liberty profile, the default context root is the name of the WAR file. For more information about options when configuring context roots, see Deploying a web application to the Liberty profile.

Icon that indicates the type of topic Reference topic

Terms and conditions for information centers | Feedback


Timestamp icon Last updated: Monday, 21 April 2014
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=phil&product=was-nd-mp&topic=rwlp_jaxrs_secure
File name: rwlp_jaxrs_secure.html