+

Search Tips   |   Advanced Search

Secure JAX-WS web services using message-level security

Web Services Security standards and profiles address how to provide message-level protection for messages that are exchanged in a web service environment.

Before beginning this task, you must develop and deploy a JAX-WS application. See the topic "JAX-WS" for more information.

JAX-WS is the next generation web services programming model complementing the foundation provided by JAX-RPC. Using JAX-WS, development of web services and clients is simplified with greater platform independence for Java applications through the use of dynamic proxies and Java annotations. JAX-WS simplifies application development through support of a standard, annotation-based model to develop web service applications and clients. A required part of the Java EE 5, JAX-WS is also known as JSR 224.

JAX-WS applications can be secured with Web Services Security in one of two ways. The application can be secured using policy sets, or through the use of the Web Services Security API (WSS API). The WSS API can only be used to secure a JAX-WS client application. The following sections describe both methods.

  1. Learn about Web Services Security.

  2. Decide which programming model, JAX-WS or JAX-RPC, works best for securing the web services applications.

  3. Configure the security bindings, or migrate an application and associated bindings.

  4. Develop and assemble a JAX-WS application.

  5. Deploy the JAX-WS application.

  6. Configure and administer the Web Services Security runtime environment.

  7. Configure policy sets through metadata exchange (WS-MetadataExchange).


Subtopics


Related concepts

  • Overview of standards and programming models for web services message-level security
  • Migration of JAX-WS Web Services Security bindings from Version 6.1
  • Auditing the Web Services Security runtime
  • General JAX-WS default bindings for Web Services Security
  • Web Services Security API programming model
  • Service Programming Interfaces (SPI)
  • Transformation of policy and binding assertions for WSDL
  • JAX-WS
  • Web services policy sets


    Related tasks

  • Secure web services using policy sets
  • Configure the username and password for WS-Security Username or LTPA token authentication
  • Configure default Web Services Security bindings
  • Secure web services applications using the WSS APIs at the message level
  • Secure requests to the trust service using system policy sets
  • Configure the Kerberos token for Web Services Security
  • Manage policy sets using the administrative console
  • Attaching a policy set to a service artifact
  • Define and manage policy set bindings
  • Signing and encrypting message parts using policy sets
  • Configure security for a WS-MetadataExchange request
  • Configure a service provider to share its policy configuration
  • Troubleshooting web services

    Tune Web Services Security for v8.5 applications