Web Services Security support
IBM® supports Web Services Security, which is an extension of the IBM Web services engine, to provide a quality of service. The WebSphere® Application Server security infrastructure fully integrates Web Services Security with the Java™ Platform, Enterprise Edition (Java EE) security specification.
WebSphere Application Server, Versions 4.x, 5, and 5.0.1 support digital signature for Apache SOAP Version 2.x. Beginning with WebSphere Application Server, Version 5.0.2, IBM supports Web Services Security. The IBM implementation is based on the Web Services Security specification, Web Services Security (WS-Security), originally proposed by IBM, Microsoft, and VeriSign in April 2002. Early versions of the proposed draft specification can be found in Web Services Security (WS-Security) Version 1.0 05 April 2002 and Web Services Security Addendum 18 August 2002. The WebSphere Application Server implementation is based on the Organization for the Advancement of Structured Information Standards (OASIS) working Draft 13 specification. (See the OASIS Web Services Security TC website for the latest working specification.) However, not all the features in the OASIS working Draft 13 specification are implemented.
Web Services Security is not supported in a pure Java client or a nonmanaged client. When a user ID and password are embedded in a request message, authentication is performed with the user ID and password. If authentication is successful, a user identity is established and further resource access is authorized based on that identity. After the user ID and password are authenticated by the Web Services Security run time, a Java EE container performs authorization.
Element | Notes® |
---|---|
UsernameToken | Both the user name and password for the BasicAuth authentication method and the user name for the identity assertion authentication method are supported. WebSphere Application Server supports nonce, a randomly generated value. |
BinarySecurityToken | X.509 certificates and Lightweight Third Party Authentication (LTPA) can be embedded, but there is no implementation to embed Kerberos tickets. However, the binary token generation and validation are pluggable and are based on the Java Authentication and Authorization Service (JAAS) Application Programming Interfaces (APIs). You can extend this implementation to generate and validate other types of binary security tokens. |
Signature | The X.509 certificate is embedded as a binary security token and can be referenced by the SecurityTokenReference. WebSphere Application Server does not support shared, key-based signature. |
Encryption | Both the EncryptedKey and ReferenceList XML tags are supported. KeyIdentifier specifies public keys and KeyName identifies the secret keys. WebSphere Application Server has the capability to map an authenticated identity to a key for encryption or use the signer certificate to encrypt the response message. |
Time stamp | WebSphere Application Server supports the Created and Expires attributes. The freshness of the message, which indicates whether the message complies with predefined time constraints, is checked only if the Expires attribute is present in the message. WebSphere Application Server does not support the Received attribute, which is defined in the addendum. Instead, WebSphere Application Server uses the TimestampTraceReceived attribute, which is defined in the OASIS specification. |
XML-based token | You can insert and validate an arbitrary format of XML tokens into a message. This format mechanism is based on the JAAS APIs. |
Method | Element |
---|---|
XML digital signature |
|
XML encryption |
|
AuthMethod |
|
Method | Element |
---|---|
XML digital signature |
|
XML encryption |
|
- Integrity of the message
- Authenticity of the message
- Confidentiality of the message
- Privacy of the message
- Transport level security: provided by Secure Sockets Layer (SSL)
- Security token propagation (pluggable)
- Identity assertion
- OASIS Web Services Security: SOAP Message Security Working Draft 13, May 2003
- http://schemas.xmlsoap.org/ws/2003/06/secext
- OASIS Web Services Security: SOAP Message Security 1.0 (WS-Security 2004)
- http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd
- OASIS Web Services Security: SOAP Message Security 1.1 (WS-Security 2004)
- http://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd
http://docs.oasis-open.org/wss/2004/01/oasis- 200401-wss-wssecurity-utility-1.0.xsd
Run time | Send | Receive |
---|---|---|
JAX-RPC draft 13 | OASIS draft 13 | OASIS draft 13 |
JAX-RPC | OASIS wssec 1.0 | OASIS wssec 1.0 OASIS draft 13 |
JAX-WS | OASIS wssec 1.1 OASIS wssec 1.0 |
OASIS wssec 1.1 OASIS wssec 1.0 OASIS draft13 |
- April 2002 specification
- http://schemas.xmlsoap.org/ws/2002/04/secext
- August 2002 addendum
- http://schemas.xmlsoap.org/ws/2002/07/secext
Refer to the Web Services Security elements table for a description of capabilities that are not supported.