blob: d26dbc3b5102e6d6d0e769e711eb9c9808171a16 [file] [log] [blame]
<?xml version="1.0" encoding="ISO-8859-1"?>
<document>
<properties>
<title>WSS4J Documentation</title>
</properties>
<body>
<section name="Apache WSS4J"/>
<section name="">
<subsection name="Contents">
<ul>
<li>
<a href="#What_is_WSS4J">What is WSS4J?</a>
</li>
<li>
<a href="#Where_can_I_download_WSS4J">Where can i download WSS4J?</a>
</li>
<li>
<a href="#WS-Security%20Features">WS-Security Features</a>
</li>
<li>
<a href="#WSS4J_Use_Cases">WSS4J Use Cases</a>
</li>
<ul>
<li>WSS4J API</li>
<li>WSS4J on Axis</li>
<li>Rampart: WS-Security Implementation module for Axis2</li>
</ul>
</ul>
<br/>
</subsection>
</section>
<section name="">
<subsection name="What is WSS4J?">
<p style="margin-left: 40px;">
Apache WSS4J is an implementation of the
OASIS Web Services Security (WS-Security) from <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss">OASIS
Web Services Security TC</a>. WSS4J is a primarily a Java library that can be used to sign and verify SOAP Messages
with WS-Security information. WSS4J will use Apache Axis and Apache XML-Security projects and will be interoperable
with JAX-RPC based server/clients and .NET server/clients.
<br/>
</p>
<p style="margin-left: 40px;">WSS4J implements<br/>
</p>
<ul style="margin-left: 40px;">
<li>
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf">OASIS
Web Serives Security: SOAP Message Security 1.0 Standard 200401, March
2004</a>
</li>
<li>
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf">Username
Token profile V1.0</a>
</li>
<li>
<a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf">X.509
Token Profile V1.0</a>
</li>
</ul>
</subsection>
<subsection name="Where can I download WSS4J">
<p style="margin-left: 40px;">Latest version of WSS4J is 1.5.3:<br/>
<a href="http://www.apache.org/dyn/closer.cgi/ws/wss4j/">http://www.apache.org/dyn/closer.cgi/ws/wss4j/</a>
</p>
</subsection>
<subsection name="WS-Security Features">
<p style="margin-left: 40px;">WSS4J can generate and process the
following SOAP Bindings:<br/>
</p>
<ul>
<ul>
<li>XML Security<br/>
</li>
<ul>
<li>XML Signature</li>
</ul>
<ul>
<li>XML Encryption</li>
</ul>
<li>Tokens</li>
<ul>
<li>Username
Tokens</li>
<li>Timestamps</li>
</ul>
<ul>
<li>SAML Tokens</li>
</ul>
</ul>
</ul>
<div style="margin-left: 40px;">WSS4J supports X.509 binary
certificates and certificate paths.<br/>
<br/>
</div>
<p style="margin-left: 40px;"/>
</subsection>
<subsection name="WSS4J API">
<p style="margin-left: 40px;">Please refer to the <a href="api.html">API
Overview</a>
for details.<br/>
<br/>
</p>
</subsection>
<subsection name="WSS4J on Axis">
<p style="margin-left: 40px;">Please refer to the the <a href="axis.html">Axis
Deployment Tutorial</a> for a short tutorial and <a href="package.html">Axis Deployment Examples</a> for more details.<br/>
</p>
<br/>
</subsection>
<subsection name="Rampart: WS-Security Implementation module for Axis2">
<p style="margin-left: 40px;">Please refer to the the
<a href="http://svn.apache.org/viewcvs.cgi/*checkout*/webservices/axis2/trunk/java/xdocs/latest/security-module.html">
Rampart configuration guide</a> for configuration information<br/>
</p>
<br/>
</subsection>
<subsection name="WSS4J Configuration">
<p style="margin-left: 40px;"><a href="cert.html">Difference between issuer-serial (WSS4J default) and direct-reference modes</a>
</p>
<br/>
</subsection>
</section>
</body>
</document>