IBM® WebSphere® Application Server provides Kerberos token support for Web services message-level security. The support is based on the Organization for the Advancement of Structured Information Standards (OASIS) Web Services Security Kerberos Token Profile Version 1.1. Use this topic to understand the Kerberos support that is available for Web services.
Kerberos Version 5 is a mature, open standard that provides a secure third-party authentication mechanism. The OASIS Web Services SOAP Message Security specification references the Kerberos token in the SOAP message. Web services applications can use the Kerberos token to send identities and protect messages more securely. Overall, Kerberos support involves Kerberos support in Java Platform, Enterprise Edition (Java EE) security and the Kerberos token support in Web services security. This topic covers the Kerberos token support in Web services security only.
In WebSphere Application Server Version 7.0, Web services security introduces support for the Kerberos token, which is based on OASIS WS-Security Kerberos Token Profile Version 1.1 specification. The Kerberos token is a binary security token for Web services message-level security. Web services security provides SOAP message-level security, such as security token propagation, message signature, and message encryption. The Kerberos token is used for message security, specifically with the SOAP message security specification for Web services, and is another supported token, such as the username token and the secure conversation token.
For more information, see the Web Services Security Kerberos Token Profile Version 1.1 specification. The specification explains how to use Kerberos security with the Web services security and how the Kerberos token is propagated and used to secure the SOAP message through signing and encryption.
The WebSphere Application Server configuration model leverages existing tools and frameworks for the Kerberos token profile configuration of authentication and message protection, such as:
For JAX-WS client applications, the design updates the application programming interfaces (APIs) for Web services security and enforces a Web services security policy with a Kerberos token, which is based on the OASIS token profile. To enable a Kerberos token profile by using a policy set, you must first establish the Web services security policy and binding files by using a custom token. For more information, see the "Kerberos configuration models for Web services" topic.