133 lines
8.7 KiB
HTML
133 lines
8.7 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Web services security and WebSphere Application Server - Express</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="wssecovwas"></a>Web services security and WebSphere Application Server - Express</h5>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express Version 5.0.x support digital signature for Apache SOAP Version 2.3. However, the strategic direction for IBM is based on the Web services security specification, <em>Web Services Security</em> (WS-Security), proposed by IBM, Microsoft, and Verisign in April 2002. In Version 5.1, WebSphere Application Server - Express supports Web services security. The implementation is based on the IBM Web services engine.</p>
|
||
|
|
|
||
|
|
<p>Web services security is a SOAP message-level security specification that is used to support security token propagation, message integrity, and message confidentiality. One intent of the specification is to address interoperability between different implementations of Web services security.</p>
|
||
|
|
|
||
|
|
<p>To realize the benefits of Web services security, it is recommended that an implementation of the specification is integrated with underlying security mechanisms. This implementation is fully integrated with the WebSphere Application Server - Express security infrastructure. Authorization, for example, is based on the J2EE security model. When a user ID and password are embedded in a request message, authentication is performed with the user ID and password. If successful, a user identity is established in the context and further resource access is authorized on that identity. After the user ID and password are authenticated by the Web services security run time, a J2EE container performs authorization.</p>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express provides an implementation of the key features of Web services security based on the following specifications:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-secure/" target="_">Specification: Web Services Security (WS-Security) Version 1.0 05 April 2002</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"> <br>(http://www-106.ibm.com/developerworks/webservices/library/ws-secure/)</p></li>
|
||
|
|
|
||
|
|
<li><p><a href="http://www-106.ibm.com/developerworks/webservices/library/ws-secureadd.html" target="_">Web Services Security Addendum 18 August 2002</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center">
|
||
|
|
<br>(http://www-106.ibm.com/developerworks/webservices/library/ws-secureadd.html)</p></li>
|
||
|
|
|
||
|
|
<li><p><a href="http://www.oasis-open.org/committees/download.php/2314/WSS-SOAPMessageSecurity-13-050103-merged.pdf" target="_">Web Services Security: SOAP Message Security Working13 May 2003</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center">
|
||
|
|
<br>(http://www.oasis-open.org/committees/download.php/2314/WSS-SOAPMessageSecurity-13-050103-merged.pdf)</p></li>
|
||
|
|
|
||
|
|
<li><p><a href="http://www.oasis-open.org/apps/group_public/download.php/1003/documents/documents/WSS-Username-02-0223-merged.pdf" target="_">Web Services Security: Username Token Profile Draft 2</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center">
|
||
|
|
<br>(http://www.oasis-open.org/apps/group_public/download.php/1003/documents/documents/WSS-Username-02-0223-merged.pdf)</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>The following list summarizes Web services security elements that are supported by WebSphere Application Server - Express:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>UsernameToken</strong>
|
||
|
|
<br>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 - Express does not support the Password Digest, Nonce, and Created attributes.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>BinarySecurityToken</strong>
|
||
|
|
<br>X.509 certificates and LTPA can be imbedded, but there is no implementation to imbed Kerberos tickets. However, the binary token generation and validation are pluggable and are based on the Java Authentication and Authorization Service (JAAS) APIs. You can extend this implementation to generate and validate other types of binary security tokens.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Signature</strong>
|
||
|
|
<br>The X.509 certificate is imbedded as a BinarySecurityToken and can be referenced by the SecurityTokenReference. WebSphere Application Server - Express does not support shared, key-based signature.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Encryption</strong>
|
||
|
|
<br>Both the EncryptedKey and ReferenceList XML tags are supported. KeyIdentifier specifies public keys and KeyName identifies the secret keys. WebSphere Application Server - Express has the capability to map an authenticated identity to a key for encryption or use the signer certificate to encrypt the response
|
||
|
|
message.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Timestamp</strong>
|
||
|
|
<br>WebSphere Application Server - Express supports the Created and Expires attributes. The freshness of the message is checked only if the Expires attribute is present in the message. WebSphere Application Server - Express does not support the Received attribute, which is defined in the addendum. Instead, WebSphere Application Server - Express uses the TimestampTrace Received attribute, which is defined in the OASIS specification.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>XML based token</strong>
|
||
|
|
<br>You can insert and validate an arbitrary format of XML tokens into a message. This format mechanism is based on the JAAS APIs.</p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>Signing and encrypting attachments is not supported in WebSphere Application Server - Express. However, WebSphere Application Server - Express signs and encrypts the following elements for the request message:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><strong>XML digital signature</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Body</li>
|
||
|
|
<li>Securitytoken</li>
|
||
|
|
<li>Timestamp</li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
<li><strong>XML encryption</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Bodycontent</li>
|
||
|
|
<li>Usernametoken</li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
<li><strong>AuthMethod</strong>
|
||
|
|
<ul>
|
||
|
|
<li>BasicAuth</li>
|
||
|
|
<li>IDAssertion (From WebSphere Application Server - Express to another WebSphere Application Server</li>
|
||
|
|
<li>Signature</li>
|
||
|
|
<li>Lightweight Third Party Authentication (LTPA) on the server side</li>
|
||
|
|
<li>Other customer tokens</li>
|
||
|
|
</ul></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express signs and encrypts the following elements for the response message:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><strong>XML digital signature</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Body</li>
|
||
|
|
<li>Timestamp</li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
<li><strong>XML encryption</strong>
|
||
|
|
<ul>
|
||
|
|
<li>Bodycontent</li>
|
||
|
|
</ul></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>The namespaces used for sending a message were published by OASIS in draft 13, published on 13 May 2003. WebSphere Application Server - Express only uses these two name spaces for sending out requests and responses:</p>
|
||
|
|
<ul>
|
||
|
|
<li><a href="http://schemas.xmlsoap.org/ws/2003/06/secext" target="_">http://schemas.xmlsoap.org/ws/2003/06/secext</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"></li>
|
||
|
|
<li><a href="http://schemas.xmlsoap.org/ws/2003/06/utility" target="_">http://schemas.xmlsoap.org/ws/2003/06/utility</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>However, WebSphere Application Server - Express can also process these other name spaces for incoming requests and responses:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li><strong>April 2002 Specification</strong>
|
||
|
|
<ul>
|
||
|
|
<li><a href="http://schemas.xmlsoap.org/ws/2002/04/secext" target="_">http://schemas.xmlsoap.org/ws/2002/04/secext</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"></li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
|
||
|
|
<li><strong>August 2002 Addendum</strong>
|
||
|
|
<ul>
|
||
|
|
<li><a href="http://schemas.xmlsoap.org/ws/2002/07/secext" target="_">http://schemas.xmlsoap.org/ws/2002/07/secext</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"></li>
|
||
|
|
<li><a href="http://schemas.xmlsoap.org/ws/2002/07/utility" target="_">http://schemas.xmlsoap.org/ws/2002/07/utility</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"></li>
|
||
|
|
</ul><p></p></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>WebSphere Application Server - Express provides the following capability for Web services security:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Integrity of the message</li>
|
||
|
|
<li>Authenticity of the message</li>
|
||
|
|
<li>Confidentiality of the message</li>
|
||
|
|
<li>Privacy of the message</li>
|
||
|
|
<li>Transport level security: provided by Secure Sockets Layer (SSL)</li>
|
||
|
|
<li>Security token propagation (pluggable)</li>
|
||
|
|
<li>Identity assertion</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|