WAS v8.5 > Secure applications > Secure web services > Secure web services > Web Services Security concepts > Web Services Security concepts

What is new for securing web services

Enhancements include...

See...

WAS supports the following OASIS specifications and WS-I profiles:

SAML is an XML-based standard for exchanging user identity and security attributes. Using SAML, a client can communicate assertions regarding the identity, attributes, and entitlements of a SOAP message. Using the SAML function in WAS, we can apply policy sets to JAX-WS applications to use SAML assertions in web services messages and in web services usage scenarios. Use SAML assertions to represent user identity and user security attributes, and optionally, to sign and to encrypt SOAP message elements.

For details on what parts of the previous specifications are supported in WAS, see Supported functionality from OASIS specifications.


High level features overview in WAS

In WAS, the Web Services Security for SOAP Message v1.1 specification is designed to be flexible and accommodate the requirements of Web services. For example, the specification does not have a mandatory security token definition. Instead, the specification defines a generic mechanism to associate the security token with a SOAP message. The use of security tokens is defined in the various v1.0 and 1.1 security token profiles, such as:

For more information on security token profile development at OASIS, see Organization for the Advancement of Structured Information Standards.

The Web Services Security for SOAP Message v1.1 updates the Web Services Security for SOAP Message core specification and the various security token profiles. For this release, WAS implements the Username Token Profile 1.1 and the X.509 Token Profile 1.1, which includes support for the Thumbprint type of security token reference. In addition, it supports the signature confirmation and encrypted header portions of the Web Services Security v1.1 standard.

The wire format (such as namespaces) in the WS-SecureConversation and WS-Trust 1.3 specification has changed. WAS tolerates requests formatted according to both the Submission Drafts and version 1.3 specifications, but ensure the correct version is used when clients are communicating with a Web Services Feature Pack service provider. We can disable tolerance of the older format for WS-SecureConversation and WS-Trust 1.3 endpoints. Submission Drafts requests are not interoperable with version 1.3 standards.

WAS supports pluggable security tokens. The pluggable architecture is enhanced to support the Web Services Security specifications, other profiles, and other Web Services Security specifications. We can learn more about the pluggable security token framework for JAX-RPC web services, and associating custom security tokens with SOAP messages, by reading these articles on the IBM developerWorks website:

WAS includes the following key enhancements:

For more information on some of these enhancements, see Web Services Security enhancements.


Configuration of Web Services Security

WAS uses the policy set model for implementing the Web Services Security v1.1 specification, including the Username token v1.1 profile, support for the Kerberos and LTPA v2 tokens, and the X.509 token version 1.1 profile. Policy sets combine configuration settings, including those for transport and message level configuration, such as WS-Addressing, WS-ReliableMessaging, WS-SecureConversation, and WS-Security. For more information on policy sets, refer to the topic Managing policy sets using the dmgr console.

We can use the dmgr console to configure the Web Services Security binding of a deployed application with Web Services Security constraints that are defined in the policy set.

For the X.509 Certificate Token Profile, one new type of security token reference is the Thumbprint reference, which is specified in the binding. WAS now supports creating and authenticating a security token using a security token reference (STR) with a key identifier and a Thumbprint in the <KeyInfo> element. The Thumbprint key information type requires there be a keystore with the public and private key pair instead of a shared key. To use the Thumbprint of the specified certificate, specify the keyInfo type THUMBPRINT in the bindings.

For example, a decryption key is referenced by means of the thumbprint of an associated certificate. The certificate is not included in the message. Instead, the <ds:KeyInfo> element contains a <wsse:SecurityTokenReference> element that specified the thumbprint of the specified certificate by means of the http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1 attribute of the <wsse:KeyIdentifier> element.

To take advantage of implementations associated with the Web Services Security v1.1 specification, you must:

WAS provides the following tools used to edit the policy set file and the binding file:

IBM assembly tools

We can use IBM assembly tools to develop web services and configure the policy set and the binding file for Web Services Security. The tools enable you to assemble both web and EJB modules. The assembly tools do not support direct editing of policy sets, but can import policy sets from the application server, and then attach the modified policy sets to the service. For more information, read about assembly tools.

We can use policy sets only with JAX-WS applications. We cannot use policy sets with JAX-RPC applications.

WAS dmgr console

We can use the dmgr console to configure the Web Services Security binding of a deployed application with Web Services Security constraints that are defined in the policy set.


What is not supported

Web service security is still fairly new and some of the standards are still being defined or standardized. The following functionality is not supported in WAS:


What is supported by the IBM SDK

The following standards exist for the Java application programming interface for XML security and Web Services Security:

For more information on the IBM SDK for Java v6, see the security information documentation.

For information on what is supported for Web Services Security in WAS, see Supported functionality from OASIS specifications.


Subtopics

  1. Web Services Security enhancements
  2. Supported functionality from OASIS specifications
  3. Web Services Security specification - a chronology


Related concepts:

Programming models for web services message-level security
Basic Security Profile compliance tips
XML token
Development and assembly tools


Related


Secure web services using Security Markup Assertion Language (SAML)
Manage policy sets


Related information:

Security information


+

Search Tips   |   Advanced Search