+

Search Tips   |   Advanced Search

Implement secure JAX-RS applications

The IBM runtime environment for Java API for RESTful Web Services (JAX-RS) is driven by a servlet derived from the Apache Wink project. Within the WAS 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.

We can define and add security constraints on the REST resources using the same tooling used to assemble REST applications. These constraints are captured in the J2EE web deployment descriptor that is associated with the application. The following list describes security definitions that we can include in the deployment descriptor:

All the security mechanisms supported by the web container are applicable to REST resources, including the use of the Kerberos-based SPNEGO authentication mechanism.

  1. Configure the development environment.

  2. Define resources in JAX-RS web applications.

  3. Configure the JAX-RS application.

  4. Secure JAX-RS applications within the web container.

  5. Secure JAX-RS resources using annotations.

  6. (Optional) Secure downstream JAX-RS resources.

  7. (Optional) Secure JAX-RS clients using SSL.

  8. Assemble JAX-RS web applications.

  9. Deploy JAX-RS web applications.

  10. Administer the secure JAX-RS application.


Results

You have developed and deployed a secure JAX-RS web application on the application server. We can also use the console to administer the secure JAX-RS application.


Subtopics


Related concepts

  • Overview of Java API for RESTful Web Services (JAX-RS)


    Related tasks

  • Secure JAX-RS applications within the web container
  • Secure downstream JAX-RS resources
  • Secure JAX-RS clients using SSL
  • Administer secure JAX-RS applications
  • Implement JAX-RS web applications

  • Web services specifications and APIs