44 lines
3.2 KiB
HTML
44 lines
3.2 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>Configure Web services security (Version 5.0.2 or later)</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h3><a name="wsseccfg"></a>Configure Web services security (Version 5.0.2 or later)</h3>
|
||
|
|
|
||
|
|
<p>Web services security for WebSphere Application Server - Express Version 5.0.2 and above is based on standards included in the <a href="http://www.ibm.com/developerworks/library/ws-secure/" target="_">Web services security specification</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"> (http://www.ibm.com/developerworks/library/ws-secure/). Web services security is a message-level standard, based on securing Simple Object Access Protocol (SOAP) messages through XML digital signature, confidentiality through XML encryption and credential propagation through security tokens.</p>
|
||
|
|
|
||
|
|
<p>The specification proposes a standard set of Simple Object Access Protocol (SOAP) extensions that you can use to build secure Web services. These standards confirm integrity and confidentiality, which are generally provided with digital signature and encryption technologies. In addition, Web services security provides a general purpose mechanism for associating security tokens with messages. A typical example of the security token is a user name and password token, in which a user name and password are included as text. Web services security defines how to encode binary security tokens such as X.509 certificates and Kerberos tickets.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> If you are using Apache SOAP 2.3 (deprecated), see <a href="wssoapsc.htm">Secure SOAP services</a> for information about configuring Web services security.</p>
|
||
|
|
|
||
|
|
<p>For an explanation of Web services security and for instructions on how to configure WebSphere Application Server - Express, see the following topics:</p>
|
||
|
|
|
||
|
|
<blockquote>
|
||
|
|
<p><strong><a href="wssecover.htm">Overview of Web services security</a></strong>
|
||
|
|
<br>See this topic for information about how WebSphere Application Server - Express implements Web services security, including the architecture, scenarios, and sample configurations.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsseccfauth.htm">Configure Web services authentication</a></strong>
|
||
|
|
<br>See this topic for instructions for configuring authentcation for Web services.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsseccfsign.htm">Configure Web services for digital signing</a></strong>
|
||
|
|
<br>You can configure your Web services to digitally sign portions of a SOAP message. See this topic for more information.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsseccfenrypt.htm">Configure Web services encryption and decryption</a></strong>
|
||
|
|
<br>WebSphere Application Server - Express supports the encryption and description of SOAP messages. See this topic for more information.</p>
|
||
|
|
|
||
|
|
<p><strong><a href="wsseccfssl.htm">Configure client-side SSL for Web services</a></strong>
|
||
|
|
<br>This topic describes how to configure SSL for Web services clients.</p>
|
||
|
|
</blockquote>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|