26 lines
3.2 KiB
HTML
26 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>Securing Web services based on WS-Security</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="wssecovwssec"></a>Securing Web services based on WS-Security</h5>
|
||
|
|
|
||
|
|
<p>Web services security for WebSphere Application Server - Express is based on standards that are in the Web services security (WS-Security) specification. These standards address how to provide protection for messages exchanged in a Web service environment. The specification defines the core facilities for protecting the integrity and confidentiality of a message and provides mechanisms for associating security-related claims with the message. 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>To secure Web services, you must consider a broad set of security requirements, including authentication, authorization, privacy, trust, integrity, confidentiality, secure communications channels, federation, delegation, and auditing across a spectrum of application and business topologies. One of the key requirements for the security model in today's business environment is the ability to interoperate between formerly incompatible security technologies (such as public key infrastructure, Kerberos and so on) in heterogeneous environments (such as Microsoft .NET and Java 2 Platform, Enterprise Edition (J2EE)). The complete Web services security protocol stack and technology roadmap is described in <a href="http://www.ibm.com/developerworks/webservices/library/ws-secmap/" target="_">Security in a Web Services World: A Proposed Architecture and Roadmap</a> <img src="www.gif" width="19" height="15" alt="Link outside Information Center"> (http://www.ibm.com/developerworks/webservices/library/ws-secmap/).</p>
|
||
|
|
|
||
|
|
<p><a href="http://www.ibm.com/developerworks/library/ws-secure/" target="_">Specification: Web Services Security (WS-Security)</a> <img src="www.gif" width="19" height="15" alt="Link outside Information Center"> (http://www.ibm.com/developerworks/library/ws-secure/) proposes a standard set of 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 using methods such as X.509 certificates and Kerberos tickets.</p>
|
||
|
|
|
||
|
|
<p>To establish a managed environment and to enforce constraints for Web services security, you must perform a Java Naming and Directory Interface (JNDI) lookup on the client to resolve the service reference.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|