You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ws.apache.org by co...@apache.org on 2012/12/04 13:49:58 UTC
svn commit: r1416918 [17/47] - in /webservices/wss4j/site: ./ apidocs/
apidocs/org/apache/ws/security/ apidocs/org/apache/ws/security/action/
apidocs/org/apache/ws/security/action/class-use/
apidocs/org/apache/ws/security/cache/ apidocs/org/apache/ws/s...
Modified: webservices/wss4j/site/package.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/package.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/package.html (original)
+++ webservices/wss4j/site/package.html Tue Dec 4 12:48:10 2012
@@ -1,17 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-
-
-
-
-
-
-
-
-
-
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 26, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Apache WSS4J - </title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -19,205 +10,137 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- </head>
+ <meta name="Date-Revision-yyyymmdd" content="20121126" />
+ <meta http-equiv="Content-Language" content="en" />
+
+ </head>
<body class="composite">
<div id="banner">
- <a href="" id="bannerLeft">
-
- Apache WSS4J
-
- </a>
- <a href="http://www.apache.org" id="bannerRight">
-
- <img src="http://activemq.apache.org/images/asf-logo.png" alt="" />
-
- </a>
+ <a href="./" id="bannerLeft">
+ Apache WSS4J
+ </a>
+ <a href="http://www.apache.org" id="bannerRight">
+ <img src="http://activemq.apache.org/images/asf-logo.png" alt="$alt" />
+ </a>
<div class="clear">
<hr/>
</div>
</div>
<div id="breadcrumbs">
-
-
-
-
-
-
-
-
- <div class="xleft">
- Last Published: 2012-07-25
+
+
+ <div class="xleft">
+ <span id="publishDate">Last Published: 2012-11-26</span>
+ | <span id="projectVersion">Version: 1.6.8</span>
</div>
- <div class="xright">
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+
+ </div>
<div class="clear">
<hr/>
</div>
</div>
<div id="leftColumn">
<div id="navcolumn">
-
-
-
-
-
-
-
-
- <h5>Apache WSS4J</h5>
- <ul>
-
- <li class="none">
- <a href="index.html">Home</a>
- </li>
-
- <li class="none">
- <a href="download.html">Download</a>
- </li>
-
- <li class="none">
- <a href="using.html">Using WSS4J</a>
- </li>
-
- <li class="none">
- <a href="config.html">WSS4J Configuration</a>
- </li>
-
- <li class="none">
- <a href="topics.html">Special Topics</a>
- </li>
-
- <li class="none">
- <a href="wss4j16.html">WSS4J 1.6 Release Notes</a>
- </li>
- </ul>
- <h5>Project Documentation</h5>
- <ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="collapsed">
- <a href="project-info.html">Project Information</a>
- </li>
-
-
-
-
+
-
-
-
-
-
-
-
-
- <li class="collapsed">
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <h5>Apache WSS4J</h5>
+ <ul>
+ <li class="none">
+ <a href="index.html" title="Home">Home</a>
+ </li>
+ <li class="none">
+ <a href="download.html" title="Download">Download</a>
+ </li>
+ <li class="none">
+ <a href="using.html" title="Using WSS4J">Using WSS4J</a>
+ </li>
+ <li class="none">
+ <a href="config.html" title="WSS4J Configuration">WSS4J Configuration</a>
+ </li>
+ <li class="none">
+ <a href="topics.html" title="Special Topics">Special Topics</a>
+ </li>
+ <li class="none">
+ <a href="best_practice.html" title="Security Best Practices">Security Best Practices</a>
+ </li>
+ <li class="none">
+ <a href="wss4j16.html" title="WSS4J 1.6 Release Notes">WSS4J 1.6 Release Notes</a>
+ </li>
</ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
- </a>
-
-
-
-
-
-
-
-
- </div>
+ <h5>Project Documentation</h5>
+ <ul>
+ <li class="collapsed">
+ <a href="project-info.html" title="Project Information">Project Information</a>
+ </li>
+ <li class="collapsed">
+ <a href="project-reports.html" title="Project Reports">Project Reports</a>
+ </li>
+ </ul>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+ </a>
+
+
+ </div>
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2><a name="Axis1_Deployment_Tutorial"></a>Axis1 Deployment Tutorial</h2>
+
+
+<div class="section"><h2>Axis1 Deployment Tutorial<a name="Axis1_Deployment_Tutorial"></a></h2>
<p>
WSS4J 1.5.x Axis handlers process SOAP requests according to the OASIS Web Service
Security (WSS) specifications.
-</p>
-<p></p>
-<p>
-The WSS4J Axis handlers <code>WSDoAllSender</code> and <code>WSDoAllReceiver
-</code> control the creation and consumption of secure SOAP requests.
+</p><p></p><p>
+The WSS4J Axis handlers <tt>WSDoAllSender</tt> and <tt>WSDoAllReceiver
+</tt> control the creation and consumption of secure SOAP requests.
The handlers work behind the scenes and are usually transparent to Web Service
(WS) applications. The Axis deployment descriptor files (*.wsdd) may contain all
necessary information to control the security processing.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
A WS application may also set properties to control the handlers
and provide default values. If the deployment descriptor sets the same
property (parameter) then the deployment descriptor overwrites the application
defined property. Thus, deployment settings overwrite application settings
to fulfill site specific requirements.
-</p>
-</div>
-<div class="section"><h2><a name="Prerequisites"></a>Prerequisites</h2>
-<p>
+</p></div>
+<div class="section"><h2>Prerequisites<a name="Prerequisites"></a></h2><p>
The WS Security Axis handlers use the WSS4J classes (Web Service Security
for Java) to process the SOAP messages. WSS4J in turn uses the Apache XML Security
project to handle XML Security according to XML Signature and XML Encryption.
-<ul><li><a class="externalLink" href="http://ws.apache.org/wss4j/index.html">WSS4J</a></li>
-<li><a class="externalLink" href="http://xml.apache.org/security/index.html">XML Security</a></li>
+</p><ul>
+ <li><a class="externalLink" href="http://ws.apache.org/wss4j/index.html">WSS4J</a></li>
+ <li><a class="externalLink" href="http://xml.apache.org/security/index.html">XML Security</a></li>
</ul>
-
The WSS4J Axis handlers require Axis V1.2 because of some problems in previous
Axis versions. WSS4J CVS contains the latest Axis libraries.
-</p>
-</div>
-<div class="section"><h2><a name="Related_Documentation"></a>Related Documentation</h2>
-<p>
+</div><div class="section"><h2>Related Documentation<a name="Related_Documentation"></a></h2><p>
The OASIS WSS specifications define a number of features and it is possible
to combine them in several ways. The WSS4J Axis handlers already support
a large number of WSS features and their combinations.
<a class="externalLink" href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss">
Here</a> are the WSS specifications.
-</p>
-</div>
-<div class="section"><h2><a name="The_basics_-_a_simple_example_that_uses"></a>The basics - a simple example that uses</h2>
-<p>
+</p></div><div class="section"><h2>The basics - a simple example that uses<a name="The_basics_-_a_simple_example_that_uses"></a></h2><p>
This chapter gives an overview and some examples how to deploy
the WSS4J Axis handlers and how the parameters and their values control the
handlers. For a better understanding of this chapter the reader shall
have a knowledge of the OASIS WSS specifications.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
The {@link org.apache.ws.security.handler.WSHandlerConstants},
{@link org.apache.ws.axis.security.WSDoAllSender}, and
{@link org.apache.ws.axis.security.WSDoAllReceiver}
provide additional and detailed documentation.
-</p>
-<div class="section"><h3><a name="Axis_deployment_descriptor_to_insert_a"></a>Axis deployment descriptor to insert a</h3>
-<p>
+</p><div class="section"><h3>Axis deployment descriptor to insert a<a name="Axis_deployment_descriptor_to_insert_a"></a></h3><p>
The following snippet shows a general layout how to deploy a WS Axis handler
on the client (application) side.
-<div class="source"><pre>
+</p><div class="source"><pre>
<!-- define the service, use the WSDoAllSender security handler in request flow -->
<service name="Ping1">
<requestFlow>
@@ -230,45 +153,39 @@ on the client (application) side.
</handler>
</requestFlow>
</service>
-</pre>
-</div>
-
+</pre></div>
This is the standard way to deploy an Axis handler. Axis parses the deployment
descriptor and provides the parameters and their value to the handler. Each
service can have its own request and response flow definition, which provides
a very flexible set-up of the security parameters.
-</p>
-<p></p>
-<p>
+<p></p><p>
The above setup inserts the most simple security structure into a SOAP request:
-the simple <code>UsernameToken</code>. This token includes a username and the
+the simple <tt>UsernameToken</tt>. This token includes a username and the
according password. Both fields are sent in cleartext, thus it provides no
real security.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
The parameters and their meanings are:
-<ul><li><code>action</code> defines the security action. The value <code>
- UsernameToken</code> directs the handler to insert this token into
+</p><ul>
+<li><tt>action</tt> defines the security action. The value <tt>
+ UsernameToken</tt> directs the handler to insert this token into
the SOAP request.
</li>
-<li><code>user</code> specifies the username to include in the token.
+<li><tt>user</tt> specifies the username to include in the token.
</li>
-<li><code>passwordType</code> is a pecific parameter for the <code>
- UsernameToken</code> action and defines the encoding of the passowrd.
- <code>PasswordText</code> specifies to send the password in
- plain text, <code>PasswordDigest</code> specifies to send the
+<li><tt>passwordType</tt> is a pecific parameter for the <tt>
+ UsernameToken</tt> action and defines the encoding of the passowrd.
+ <tt>PasswordText</tt> specifies to send the password in
+ plain text, <tt>PasswordDigest</tt> specifies to send the
password in digest mode (refer to WSS UsernameToken Profile)
</li>
-<li><code>passwordCallbackClass</code> contains the name of a class that
+<li><tt>passwordCallbackClass</tt> contains the name of a class that
implements a method to get the user's password. Please refer to the
detailed documentation in
{@link org.apache.ws.security.handler.WSHandlerConstants#PW_CALLBACK_CLASS}.
</li>
</ul>
-
The WSS4J Axis security handler interprets the parameter values and controls
the WSS4J modules to generate the following SOAP request:
<div class="source"><pre>
@@ -293,34 +210,27 @@ the WSS4J modules to generate the follow
</Ping>
</soapenv:Body>
</soapenv:Envelope>
-</pre>
-</div>
-
+</pre></div>
This is a pretty print of the real SOAP message.
-</p>
-</div>
-<div class="section"><h3><a name="The_password_callback_class"></a>The password callback class</h3>
-<p>
+</div><div class="section"><h3>The password callback class<a name="The_password_callback_class"></a></h3><p>
The deployment descriptor contains the user name that the handler inserts into
-the <code>UsernameToken</code> but not the password. In general it is not a
+the <tt>UsernameToken</tt> but not the password. In general it is not a
good idea to store sensitive information like a password in cleartext. To
get the password the WSS4J Axis handler uses a password callback
technique similar to the JAAS mechansim. The parameter
-<code>passwordCallbackClass</code> contains the classname of the callback
+<tt>passwordCallbackClass</tt> contains the classname of the callback
class. This class must implement the
{@link javax.security.auth.callback.CallbackHandler}
interface. The WSS4J Axis handler gets this class,
-instantiates it, and calls the <code>handle</code> method when it
+instantiates it, and calls the <tt>handle</tt> method when it
needs a password. Refer also to the
{@link org.apache.ws.security.handler.WSHandlerConstants#PW_CALLBACK_CLASS
parameter} documentation.
- </p>
-<p></p>
-<p>
+ </p><p></p><p>
The following code snippet shows a simple password callback class:
- <div class="source"><pre>
+ </p><div class="source"><pre>
package org.apache.ws.axis.oasis;
import java.io.IOException;
@@ -366,43 +276,32 @@ public class PWCallback implements Callb
}
}
}
-</pre>
-</div>
-
+</pre></div>
The Java {@link javax.security.auth.callback.CallbackHandler callback} handler
documentation provides a detailed description of the interface and exceptions.
-</p>
-<p></p>
-<p>
+<p></p><p>
The WSS4J library uses a specific class to get the required password or key
-informations. The <code>WSSPasswordCallback</code> class implements the
+informations. The <tt>WSSPasswordCallback</tt> class implements the
{@link javax.security.auth.callback.Callback} interface according to the
JAAS. Depending on it usage this class either carries the required password
-as a Java <code>String </code> or it carries the required key information
-as a Java <code>byte[]</code> array. Refer to
+as a Java <tt>String </tt> or it carries the required key information
+as a Java <tt>byte[]</tt> array. Refer to
{@link org.apache.ws.security.WSPasswordCallback} that contains a
detailed description of the usage codes.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
The WSS4J Axis handler or the WSS4J modules set the usage code before
-they call <code>handle</code> method.
+they call <tt>handle</tt> method.
-</p>
-</div>
-<div class="section"><h3><a name="Application_sets_parameters_to_insert_in"></a>Application sets parameters to insert in</h3>
-<p>
+</p></div><div class="section"><h3>Application sets parameters to insert in<a name="Application_sets_parameters_to_insert_in"></a></h3><p>
Sometimes it is not feasable or not possible to determine parameters
and their values during deployment. In this case the application can
set paramters during runtime. The WSS4J Axis handlers use the Axis
-<code>setProperty</code> method to support this feature.
-</p>
-<p></p>
-<p>
+<tt>setProperty</tt> method to support this feature.
+</p><p></p><p>
The following code snippet shows an example how to use the dynamic setting
of parameters and their values:
-<div class="source"><pre>
+</p><div class="source"><pre>
...
Service service = new Service();
Call call = (Call) service.createCall();
@@ -410,12 +309,10 @@ of parameters and their values:
call.setProperty(UsernameToken.PASSWORD_TYPE, WSConstants.PASSWORD_TEXT);
call.setProperty(WSHandlerConstants.USER, "werner");
...
-</pre>
-</div>
-
-Use this way if your application dynamically creates a <code>call</code>
-object. If your application uses stubs generated by Axis' <code>WSDL2Java
-</code> tool, the application uses the following functions:
+</pre></div>
+Use this way if your application dynamically creates a <tt>call</tt>
+object. If your application uses stubs generated by Axis' <tt>WSDL2Java
+</tt> tool, the application uses the following functions:
<div class="source"><pre>
...
PingServiceLocator service = new PingServiceLocator();
@@ -424,25 +321,18 @@ object. If your application uses stubs g
port._setProperty(UsernameToken.PASSWORD_TYPE, WSConstants.PASSWORD_TEXT);
port._setProperty(WSHandlerConstants.USER, "werner");
...
-</pre>
-</div>
-
-Please note that <code>_setProperty</code> is a Axis specific call.
+</pre></div>
+Please note that <tt>_setProperty</tt> is a Axis specific call.
-</p>
-</div>
-<div class="section"><h3><a name="The_password_callback_object_reference"></a>The password callback object reference</h3>
-<p>
+</div><div class="section"><h3>The password callback object reference<a name="The_password_callback_object_reference"></a></h3><p>
In addition to the <a href="#pwCallBackClass">password callback class</a>
-an application may set a password callback object using the <code>
- setProperty()</code> methods. Only applications (and Axis handlers that
+an application may set a password callback object using the <tt>
+ setProperty()</tt> methods. Only applications (and Axis handlers that
preceed the WSS4J Axis handlers in a handler chain) can use this feature.
- </p>
-<p></p>
-<p>
+ </p><p></p><p>
For example:
- <div class="source"><pre>
+ </p><div class="source"><pre>
public class Scenario1 implements CallbackHandler {
public static void main(String args[]) {
@@ -460,17 +350,14 @@ public class Scenario1 implements Callba
...
}
}
-</pre>
-</div>
-</p>
-</div>
-<div class="section"><h3><a name="Deployment_of_the_WSS4J_Axis__handler"></a>Deployment of the WSS4J Axis handler</h3>
-<p>
+</pre></div>
-Similar to the deployment descriptor of the sending handler <code>WSDoAllSender
-</code> a deployment descriptor for the receiving handler exists. For the above
+</div><div class="section"><h3>Deployment of the WSS4J Axis handler<a name="Deployment_of_the_WSS4J_Axis__handler"></a></h3><p>
+
+Similar to the deployment descriptor of the sending handler <tt>WSDoAllSender
+</tt> a deployment descriptor for the receiving handler exists. For the above
example the deployment descriptor look like:
-<div class="source"><pre>
+</p><div class="source"><pre>
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter name="passwordCallbackClass"
@@ -478,40 +365,30 @@ example the deployment descriptor look l
<parameter name="action" value="UsernameToken"/>
</handler>
</requestFlow>
-</pre>
-</div>
-
+</pre></div>
The receiving WSS4J Axis handler checks if the SOAP request matches the defined
actions.
-</p>
-</div>
-</div>
-<div class="section"><h2><a name="Combining_security_actions"></a>Combining security actions</h2>
-<p>
+</div></div><div class="section"><h2>Combining security actions<a name="Combining_security_actions"></a></h2><p>
Often it is necessary to combine or concatenate several security actions, for
example to encrypt parts of a message and sign some other parts. The WSS4J
Axis handlers provide easy and simple methods to combine or concatenate
security actions.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
This chapter describes simple combinations of actions.
-</p>
-<div class="section"><h3><a name="Combine__and"></a>Combine and</h3>
-<p>
+</p><div class="section"><h3>Combine and<a name="Combine__and"></a></h3><p>
The WS Interoperability specifications define this use case:
-<ul><li>Insert a <code>UsernameToken</code>, use <code>PasswordText</code>
+</p><ul>
+ <li>Insert a <tt>UsernameToken</tt>, use <tt>PasswordText</tt>
to set the password. In addition add a timestamp and a nonce into
- the <code>UsernameToken</code></li>
-<li>Encrypt the <code>UsernameToken</code> to protect the information.
+ the <tt>UsernameToken</tt></li>
+ <li>Encrypt the <tt>UsernameToken</tt> to protect the information.
</li>
</ul>
-
The Axis deplyment descriptor for this use case:
<div class="source"><pre>
<requestFlow>
@@ -530,42 +407,40 @@ The Axis deplyment descriptor for this u
value="{Element}{http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd}UsernameToken" />
</handler>
</requestFlow>
-</pre>
-</div>
-
+</pre></div>
-This descriptor contains some new parameters to control the <code>UsernameToken
-</code> element and its encryption. The new parameters and their meaning are:
-<ul><li><code>addUTElement</code> - controls if the handler shall insert elements
- into the <code>UsernameToken</code>. The value is a blank separated list of
- element names to include. Only <code>Nonce</code> and <code>Created</code> are
+This descriptor contains some new parameters to control the <tt>UsernameToken
+</tt> element and its encryption. The new parameters and their meaning are:
+<ul>
+ <li><tt>addUTElement</tt> - controls if the handler shall insert elements
+ into the <tt>UsernameToken</tt>. The value is a blank separated list of
+ element names to include. Only <tt>Nonce</tt> and <tt>Created</tt> are
supported.</li>
-<li><code>encryptionPropFile</code> - the name of a crypto property file. This
+ <li><tt>encryptionPropFile</tt> - the name of a crypto property file. This
file contains parameters and property that control the encryption. Please refer
to the
{@link org.apache.ws.security.handler.WSHandlerConstants#ENC_PROP_FILE
detailed} description of the cyrpto property file.</li>
-<li><code>encryptionKeyIdentifier</code> - specifies the format in which the
+ <li><tt>encryptionKeyIdentifier</tt> - specifies the format in which the
handler inserts the encryption key into the SOAP request. Please refer
to the
{@link org.apache.ws.security.handler.WSHandlerConstants#ENC_KEY_ID
detailed} description.</li>
-<li><code>encryptionUser</code> - the name or identifier of the user who owns
+ <li><tt>encryptionUser</tt> - the name or identifier of the user who owns
the public key to encrypt the data. Usually this is the name or alias name
of the owner's certificate in a keystore.</li>
-<li><code>encryptionParts</code> - controls which part or parts the handler
+ <li><tt>encryptionParts</tt> - controls which part or parts the handler
of the SOAP shall encrypt. If this parameter is not defined, WSS4J encrypts
- the whole SOAP Body in <code>Content</code> mode. The value of the
- parameter in this example specifies to encrypt the element <code>
- UsernameToken</code>, contained in the namespace
- <code>http://schemas.xmlsoap.org/ws/2002/07/secext</code>. The encryption
- module uses the <code>Element</code> mode to encrypt the element data.
+ the whole SOAP Body in <tt>Content</tt> mode. The value of the
+ parameter in this example specifies to encrypt the element <tt>
+ UsernameToken</tt>, contained in the namespace
+ <tt>http://schemas.xmlsoap.org/ws/2002/07/secext</tt>. The encryption
+ module uses the <tt>Element</tt> mode to encrypt the element data.
Please refer to the
{@link org.apache.ws.security.handler.WSHandlerConstants#ENCRYPTION_PARTS
detailed} description.
</li>
</ul>
-
The matching receiver deployment descriptor:
<div class="source"><pre>
<requestFlow>
@@ -576,29 +451,22 @@ The matching receiver deployment descrip
<parameter name="decryptionPropFile" value="crypto.properties" />
</handler>
</requestFlow>
-</pre>
-</div>
-
-The only new parameter here is the <code>decryptionPropFile</code>. This
+</pre></div>
+The only new parameter here is the <tt>decryptionPropFile</tt>. This
parameter defines the crypto property file at the receiver side. The value
- of the <code>action</code> parameter matches the according value at the
+ of the <tt>action</tt> parameter matches the according value at the
sender side. The WSS4J Axis receiver checks if the SOAP request contains
the required security data.
-</p>
-</div>
-<div class="section"><h3><a name="Combine_Signature_and_Encryption"></a>Combine Signature and Encryption</h3>
-<p>
+</div><div class="section"><h3>Combine Signature and Encryption<a name="Combine_Signature_and_Encryption"></a></h3><p>
This is a very common usage of Web Service security. The WSS4J Axis handler
provides flexible parameter settings that support several ways to use
the Signature/Encryption combination.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
A WSS4J Axis deployment descriptor for a simple Singature/Encryption of
SOAP requests:
-<div class="source"><pre>
+</p><div class="source"><pre>
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
<parameter name="user" value="16c73ab6-b892-458f-abf5-2f875f74882e"/>
@@ -608,45 +476,35 @@ SOAP requests:
<parameter name="signaturePropFile" value="crypto.properties" />
</handler>
</requestFlow>
-</pre>
-</div>
-
+</pre></div>
This simple deployment descriptor signs and encrypts the SOAP Body part.
-The only new parameter, <code>signaturePropFile</code>, specifies the
+The only new parameter, <tt>signaturePropFile</tt>, specifies the
name of the signature crypto property file to use. Because no
-<code>encryptionPropFile</code> is declared the handler also uses the signature
+<tt>encryptionPropFile</tt> is declared the handler also uses the signature
property file to get the encryption certificate. The same holds true for
the username. The password callback class must return a password
to get the user's private key (the keystore is defined in the crypto
property file) that WSS4J uses to generate the signature. The encryption
method uses the user's public key to encrypt the dynamically generated
session key.
-</p>
-<p></p>
-<p>
-The <code>action</code> parameter defines <code>Signature Encryption</code>.
+<p></p><p>
+The <tt>action</tt> parameter defines <tt>Signature Encryption</tt>.
Thus the handler first signs, then the encrypts the data.
Because the deployment descriptor does not contain specific encryption or
signature part parameters, WSS4J defaults to the data of the SOAP Body element.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
Also all other parameters use their default setting, such as the format of the
key identifiers, encryption modifiers, and so on. Please refer to the
{@link org.apache.ws.security.handler.WSHandlerConstants detailed}
documentation of the parameters.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
If the WSS4J Axis handler shall perform encryption only, then the
deployment descriptor must contain the encryption specific parameters. Only
if sign <b>and</b> encryption is required the encryption method falls back to
the signature parameters if the encryption specific parameters are not set.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
The matching receiver deployment descriptor is also very simple:
-<div class="source"><pre>
+</p><div class="source"><pre>
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter name="passwordCallbackClass"
@@ -655,48 +513,35 @@ The matching receiver deployment descrip
<parameter name="signaturePropFile" value="crypto.properties" />
</handler>
</requestFlow>
-</pre>
-</div>
-
+</pre></div>
To reverse the actions, just reverse the action specifiers. The WSS4J
handler encrypts the SOAP Body first, then signs the encrypted data.
-</p>
-</div>
-</div>
-<div class="section"><h2><a name="Signing_and_encrypting_multiple_XML_elements"></a>Signing and encrypting multiple XML elements</h2>
-<p>
+</div></div><div class="section"><h2>Signing and encrypting multiple XML elements<a name="Signing_and_encrypting_multiple_XML_elements"></a></h2><p>
Sometimes it is necessary to sign and/or encrypt several parts of a SOAP
-message. The deployment parameters <code>signatureParts</code> and
-<code>encryptionParts</code> control which SOAP elements to sign or
+message. The deployment parameters <tt>signatureParts</tt> and
+<tt>encryptionParts</tt> control which SOAP elements to sign or
to encrypt. Please refer to the
{@link org.apache.ws.security.handler.WSHandlerConstants#ENCRYPTION_PARTS
detailed} description of these parameters.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
WSS4J signs or encrypts all declared parts using the same keys, that is
the signature or encryption data structures directly reference the
specified parts as described in the WSS specifications. The receiver
automatically detects these references and verfies and decrypts the
data parts. No special settings in the depolyment descriptor is necessary.
-</p>
-</div>
-<div class="section"><h2><a name="Chaining_of_WSS4J_Axis_handlers"></a>Chaining of WSS4J Axis handlers</h2>
-<p>
+</p></div><div class="section"><h2>Chaining of WSS4J Axis handlers<a name="Chaining_of_WSS4J_Axis_handlers"></a></h2><p>
This is a very powerful feature that supports even more flexible signature and
encryption processing such as signatures with multiple keys (overlapping
signatures), multiple encryption algorithms, or different SOAP actor (role)
defintions of the security headers.
-</p>
-<div class="section"><h3><a name="Deployment_at_the_client"></a>Deployment at the client</h3>
-<p>
+</p><div class="section"><h3>Deployment at the client<a name="Deployment_at_the_client"></a></h3><p>
A deployment descriptor to chain handlers:
-<div class="source"><pre>
+</p><div class="source"><pre>
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllSender" >
<parameter name="action" value="Signature NoSerialization"/>
@@ -714,62 +559,49 @@ A deployment descriptor to chain handler
<parameter name="signaturePropFile" value="crypto.properties" />
</handler>
</requestFlow>
-</pre>
-</div>
-
-Note the action specifier <code>NoSerialization</code> first handler.
+</pre></div>
+Note the action specifier <tt>NoSerialization</tt> first handler.
In a handler chain of WSS4J handlers every
but the last handler <i>must</i> have this action specifier. This specifier
surpresses the very last step of the handler's security processing: the
serialization of the processed SOAP request in a XML string (document) that
Axis sends to the reveiver. Only the last handler must perform this
serialization.
-</p>
-<p></p>
-<p>
+<p></p><p>
Every handler specification can have its own set of parameters that define
the individual values for this handler instance. Thus the deployment
descriptor can define different crypto property files, different usernames,
-and so on. In the example the first handler signs the <code>ticket</code>
+and so on. In the example the first handler signs the <tt>ticket</tt>
element and the second handler the SOAP Body (default).
-</p>
-<p></p>
-<p>
-Parameters set by the application with <code>setProperty</code> are valid for
+</p><p></p><p>
+Parameters set by the application with <tt>setProperty</tt> are valid for
<b>all</b> handler instances in the handler
-chain (<code>setProperty</code> is defined on the SOAP request (call) level).
+chain (<tt>setProperty</tt> is defined on the SOAP request (call) level).
As already decribed, deployment settings overrule application settings. Thus it
is possible to combine various parameter specifications. A special case is the
definition of the username. If an application sets the username and one
-handler instance in the chain does not have a <code>user</code> parameter
+handler instance in the chain does not have a <tt>user</tt> parameter
in its deployment part, then this one handler instance uses the username set
bey the application. After the handler copied the username from the username
-property, the handler sets the property's content to <code>null</code>.
+property, the handler sets the property's content to <tt>null</tt>.
Handlers that follow in the chain cannot use this username anymore and
must have a user (or encryption user) parameter in their deployment part.
-</p>
-</div>
-<div class="section"><h3><a name="Deployment_at_the_server"></a>Deployment at the server</h3>
-<p>
+</p></div><div class="section"><h3>Deployment at the server<a name="Deployment_at_the_server"></a></h3><p>
Note: Handler chaining at the receiver side is not yet fully tested.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
Handlers at the receiver can only determine different security headers if their
SOAP actors are different. The WSS4J handler processes each security structure
inside one security header. Because the security structures contain most
information to verify or decrypt the SOAP request this constraint is
not too much of an issue.
-</p>
-<p></p>
-<p>
-Only the password call back class and the <code>Crypto</code> implementation
+</p><p></p><p>
+Only the password call back class and the <tt>Crypto</tt> implementation
(as defined in the crypto property file) must be able to handle all possible
certificates, users, passwords, and keys that a security header may contain.
The following deployment descriptor of a receiver shows this.
-<div class="source"><pre>
+</p><div class="source"><pre>
<requestFlow>
<handler type="java:org.apache.ws.axis.security.WSDoAllReceiver">
<parameter name="passwordCallbackClass"
@@ -778,39 +610,29 @@ The following deployment descriptor of a
<parameter name="signaturePropFile" value="crypto.properties" />
</handler>
</requestFlow>
-</pre>
-</div>
-
+</pre></div>
The client uses two handlers in a chain, each signing a part of the SOAP
request but with different certificates. Because the handlers do not
specifiy a SOAP actor WSS4J puts both signatures in the security header
of the default actor.
To match the security actions the deployment descriptor of the receiver needs
-to contain the action declaration <code>Signature Signature</code>. This
+to contain the action declaration <tt>Signature Signature</tt>. This
instructs the WSS4J handler to accept and verify two distinct signatures
contained in one security header. Because the signatures use different
-certificates the <code>Crypto</code> implementation must be able to handle
+certificates the <tt>Crypto</tt> implementation must be able to handle
these certificates.
-</p>
-<p></p>
-<p>
+<p></p><p>
Similar requirements are true for the password callback implementation if the
sender uses handler chaining and uses different encryption parameters in the
same security header.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
If it is necessary to have different parameters for the distinct signature or
decryption data then these should be put in different security headers. The
-easiest way to do this is to define different <code>actor</code> parameters
+easiest way to do this is to define different <tt>actor</tt> parameters
for each handler in a WSS4J handler chain.
-</p>
-</div>
-</div>
-<div class="section"><h2><a name="Reporting_Security_results_to_servicesapplications"></a>Reporting Security results to services/applications</h2>
-<p>
-The WSS4J <code>WSSecurityEngine</code> processes the security elements inside
+</p></div></div><div class="section"><h2>Reporting Security results to services/applications<a name="Reporting_Security_results_to_servicesapplications"></a></h2><p>
+The WSS4J <tt>WSSecurityEngine</tt> processes the security elements inside
a security header. If something goes wrong, for example a signature
verfication fails, then the engine throws a fault. If the security engine
could perform all operations sucessfully it returns a data structure
@@ -819,10 +641,8 @@ structure holds information about the pe
identifier in case the security engine performed signature or username token
processing. Please refer to the
{@link org.apache.ws.security.WSSecurityEngineResult result} structure.
-</p>
-<p></p>
-<p>
-The <code>WSDoAllReceiver</code> WSS4J handler takes this structure and
+</p><p></p><p>
+The <tt>WSDoAllReceiver</tt> WSS4J handler takes this structure and
checks if all required actions were performed. If this check fails, the
WSS4J handler aborts the SOAP request and throws an Axis SOAP fault.
Otherwise it creates its own data structure
@@ -834,12 +654,10 @@ this vector in a specific
of the current message context. If WSS4J handlers are
chained, then every handler in the chain adds its result to the vector. The
vector contains the results in handler-chain order.
-</p>
-<p></p>
-<p>
+</p><p></p><p>
This code snippet shows how a Axis service can access the security result
data:
-<div class="source"><pre>
+</p><div class="source"><pre>
public void ping(javax.xml.rpc.holders.StringHolder text,
org.apache.ws.axis.oasis.ping.TicketType ticket)
throws java.rmi.RemoteException {
@@ -872,20 +690,14 @@ data:
}
}
}
-</pre>
-</div>
-
+</pre></div>
The principal structure is either a
{@link org.apache.ws.security.WSUsernameTokenPrincipal UsernameToken} principal
or a {@link java.security.Principal X509Principal}. The
princpals contain the names plus other information of the verified username
token or signature certificate.
-</p>
-</div>
-<div class="section"><h2><a name="Some_hints"></a>Some hints</h2>
-<div class="section"><h3><a name="Client"></a>Client</h3>
-<p>
+</div><div class="section"><h2>Some hints<a name="Some_hints"></a></h2><div class="section"><h3>Client<a name="Client"></a></h3><p>
At the client side, the WSS4J Axis handler, as all other parts of Axis, run
in the context of the calling application. Depending on the application,
the callback classes may perform complex operations, even do some user
@@ -893,36 +705,27 @@ interaction, to get the password or to a
certificates or keys. There are no timeouts defined at the client side
before the SOAP request is put on the wire.
-</p>
-</div>
-<div class="section"><h3><a name="Server"></a>Server</h3>
-<p>
+</p></div><div class="section"><h3>Server<a name="Server"></a></h3><p>
On the server side the WSS4J handler run in the same context as the other part
of the server, usually some servlet container, such as Tomcat. Also the server
must be able to handle many requests in a short time. Thus the password
-callback as well as the <code>Crypto</code> implementation shall be
+callback as well as the <tt>Crypto</tt> implementation shall be
as fast as possible. In general, no user interaction is possible at the
server side to gather passwords. Also at this point of the SOAP request
processing there are active timeouts, even if they are fairly long.
-</p>
-</div>
-<div class="section"><h3><a name="Bi-directional_SOAP_Security"></a>Bi-directional SOAP Security</h3>
-<p>
+</p></div><div class="section"><h3>Bi-directional SOAP Security<a name="Bi-directional_SOAP_Security"></a></h3><p>
WSS4J fully supports bi-directional SOAP security. To enable bi-directional
-support just put <code>WSDoAllSender</code> on the
-<code>responseFlow</code> at the server and <code>WSDoAllReceiver</code>
+support just put <tt>WSDoAllSender</tt> on the
+<tt>responseFlow</tt> at the server and <tt>WSDoAllReceiver</tt>
at the response flow of the client thus reversing the roles. Similar to
-the above hints, the server side part (now <code>WSDoAllSender</code>)
-runs in the server context and <code>WSDoAllReceiver</code>
+the above hints, the server side part (now <tt>WSDoAllSender</tt>)
+runs in the server context and <tt>WSDoAllReceiver</tt>
runs in the application (client) context. There are no Axis timeout
constraints on the client side after Axis received the response
and handed it over to the WSS4J handler.
-</p>
-</div>
-<div class="section"><h3><a name="Handler_chaining"></a>Handler chaining</h3>
-<p>
+</p></div><div class="section"><h3>Handler chaining<a name="Handler_chaining"></a></h3><p>
Usually WSS4J handlers are chained without any other handler between them in
the chain. It is, however, possible to do so. In this case the intermediate
handler <b>must not</b> modify the SOAP Envelope that is contained in the
@@ -931,10 +734,10 @@ security actions done sofar. Such an int
properties that may influence the processing of the following WSS4J handler,
such as setting a new username, password callback class, and so on.
-
-@since WSS4J 1.0</p>
-</div>
+<!-- Put @see and @since tags down here. -->
+@since WSS4J 1.0</p></div>
</div>
+
</div>
</div>
@@ -942,19 +745,12 @@ such as setting a new username, password
<hr/>
</div>
<div id="footer">
- <div class="xright">©
- 2004-2012
-
- The Apache Software Foundation
-
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+ Copyright © 2004-2012
+ <a href="http://www.apache.org/">The Apache Software Foundation</a>.
+ All Rights Reserved.
+
+ </div>
<div class="clear">
<hr/>
</div>
Modified: webservices/wss4j/site/pmd.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/pmd.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/pmd.html (original)
+++ webservices/wss4j/site/pmd.html Tue Dec 4 12:48:10 2012
@@ -37,7 +37,7 @@
<div class="xleft">
- Last Published: 2012-07-25
+ Last Published: 2012-11-26
</div>
<div class="xright">
Modified: webservices/wss4j/site/pmd.xml
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/pmd.xml?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/pmd.xml (original)
+++ webservices/wss4j/site/pmd.xml Tue Dec 4 12:48:10 2012
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="UTF-8"?>
-<pmd version="4.2.5" timestamp="2012-07-25T15:27:32.905">
-<suppressedviolation filename="/tmp/1_6_7/src/main/java/org/apache/ws/security/WSSConfig.java" suppressiontype="nopmd" msg="Avoid empty catch blocks" usermsg="
+<pmd version="4.2.5" timestamp="2012-11-26T14:56:35.793">
+<suppressedviolation filename="/tmp/1_6_8/src/main/java/org/apache/ws/security/WSSConfig.java" suppressiontype="nopmd" msg="Avoid empty catch blocks" usermsg="
"/>
-<suppressedviolation filename="/tmp/1_6_7/src/main/java/org/apache/ws/security/WSSConfig.java" suppressiontype="nopmd" msg="Avoid empty catch blocks" usermsg="
+<suppressedviolation filename="/tmp/1_6_8/src/main/java/org/apache/ws/security/WSSConfig.java" suppressiontype="nopmd" msg="Avoid empty catch blocks" usermsg="
"/>
</pmd>
\ No newline at end of file
Modified: webservices/wss4j/site/project-info.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/project-info.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/project-info.html (original)
+++ webservices/wss4j/site/project-info.html Tue Dec 4 12:48:10 2012
@@ -1,17 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-
-
-
-
-
-
-
-
-
-
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 26, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Apache WSS4J - Project Information</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -19,202 +10,132 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- </head>
+ <meta name="Date-Revision-yyyymmdd" content="20121126" />
+ <meta http-equiv="Content-Language" content="en" />
+
+ </head>
<body class="composite">
<div id="banner">
- <a href="" id="bannerLeft">
-
- Apache WSS4J
-
- </a>
- <a href="http://www.apache.org" id="bannerRight">
-
- <img src="http://activemq.apache.org/images/asf-logo.png" alt="" />
-
- </a>
+ <a href="./" id="bannerLeft">
+ Apache WSS4J
+ </a>
+ <a href="http://www.apache.org" id="bannerRight">
+ <img src="http://activemq.apache.org/images/asf-logo.png" alt="$alt" />
+ </a>
<div class="clear">
<hr/>
</div>
</div>
<div id="breadcrumbs">
-
-
-
-
-
-
-
-
- <div class="xleft">
- Last Published: 2012-07-25
+
+
+ <div class="xleft">
+ <span id="publishDate">Last Published: 2012-11-26</span>
+ | <span id="projectVersion">Version: 1.6.8</span>
</div>
- <div class="xright">
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+
+ </div>
<div class="clear">
<hr/>
</div>
</div>
<div id="leftColumn">
<div id="navcolumn">
-
-
-
-
-
-
-
-
- <h5>Apache WSS4J</h5>
- <ul>
-
- <li class="none">
- <a href="index.html">Home</a>
- </li>
-
- <li class="none">
- <a href="download.html">Download</a>
- </li>
-
- <li class="none">
- <a href="using.html">Using WSS4J</a>
- </li>
-
- <li class="none">
- <a href="config.html">WSS4J Configuration</a>
- </li>
-
- <li class="none">
- <a href="topics.html">Special Topics</a>
- </li>
-
- <li class="none">
- <a href="wss4j16.html">WSS4J 1.6 Release Notes</a>
- </li>
+
+
+ <h5>Apache WSS4J</h5>
+ <ul>
+ <li class="none">
+ <a href="index.html" title="Home">Home</a>
+ </li>
+ <li class="none">
+ <a href="download.html" title="Download">Download</a>
+ </li>
+ <li class="none">
+ <a href="using.html" title="Using WSS4J">Using WSS4J</a>
+ </li>
+ <li class="none">
+ <a href="config.html" title="WSS4J Configuration">WSS4J Configuration</a>
+ </li>
+ <li class="none">
+ <a href="topics.html" title="Special Topics">Special Topics</a>
+ </li>
+ <li class="none">
+ <a href="best_practice.html" title="Security Best Practices">Security Best Practices</a>
+ </li>
+ <li class="none">
+ <a href="wss4j16.html" title="WSS4J 1.6 Release Notes">WSS4J 1.6 Release Notes</a>
+ </li>
</ul>
- <h5>Project Documentation</h5>
- <ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="expanded">
- <strong>Project Information</strong>
- <ul>
-
- <li class="none">
- <a href="dependencies.html">Dependencies</a>
- </li>
-
- <li class="none">
- <a href="issue-tracking.html">Issue Tracking</a>
- </li>
-
- <li class="none">
- <a href="mail-lists.html">Mailing Lists</a>
- </li>
-
- <li class="none">
- <a href="license.html">Project License</a>
- </li>
-
- <li class="none">
- <a href="source-repository.html">Source Repository</a>
- </li>
+ <h5>Project Documentation</h5>
+ <ul>
+ <li class="expanded">
+ <strong>Project Information</strong>
+ <ul>
+ <li class="none">
+ <a href="plugin-management.html" title="Plugin Management">Plugin Management</a>
+ </li>
+ <li class="none">
+ <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+ </li>
+ <li class="none">
+ <a href="integration.html" title="Continuous Integration">Continuous Integration</a>
+ </li>
+ <li class="none">
+ <a href="license.html" title="Project License">Project License</a>
+ </li>
+ <li class="none">
+ <a href="team-list.html" title="Project Team">Project Team</a>
+ </li>
+ <li class="none">
+ <a href="source-repository.html" title="Source Repository">Source Repository</a>
+ </li>
+ <li class="none">
+ <a href="index.html" title="About">About</a>
+ </li>
+ <li class="none">
+ <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+ </li>
+ <li class="none">
+ <a href="project-summary.html" title="Project Summary">Project Summary</a>
+ </li>
+ <li class="none">
+ <a href="plugins.html" title="Project Plugins">Project Plugins</a>
+ </li>
+ <li class="none">
+ <a href="dependencies.html" title="Dependencies">Dependencies</a>
+ </li>
</ul>
</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="collapsed">
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li class="collapsed">
+ <a href="project-reports.html" title="Project Reports">Project Reports</a>
+ </li>
</ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
- </a>
-
-
-
-
-
-
-
-
- </div>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+ </a>
+
+
+ </div>
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Project Information</h2>
-<p>This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> on behalf of the project.</p>
-<div class="section"><h3>Overview</h3>
-<table class="bodyTable"><tr class="a"><th>Document</th>
-<th>Description</th>
-</tr>
-<tr class="b"><td><a href="dependencies.html">Dependencies</a></td>
-<td>This document lists the project's dependencies and provides information on each dependency.</td>
-</tr>
-<tr class="a"><td><a href="issue-tracking.html">Issue Tracking</a></td>
-<td>This is a link to the issue management system for this project. Issues (bugs, features, change requests) can be created and queried using this link.</td>
-</tr>
-<tr class="b"><td><a href="mail-lists.html">Mailing Lists</a></td>
-<td>This document provides subscription and archive information for this project's mailing lists.</td>
-</tr>
-<tr class="a"><td><a href="license.html">Project License</a></td>
-<td>This is a link to the definitions of project licenses.</td>
-</tr>
-<tr class="b"><td><a href="source-repository.html">Source Repository</a></td>
-<td>This is a link to the online source repository that can be viewed via a web browser.</td>
-</tr>
-</table>
-</div>
-</div>
-
+ <div class="section"><h2>Project Information<a name="Project_Information"></a></h2><p>This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> on behalf of the project.</p><div class="section"><h3>Overview<a name="Overview"></a></h3><table border="0" class="bodyTable"><tr class="a"><th>Document</th><th>Description</th></tr><tr class="b"><td><a href="plugin-management.html">Plugin Management</a></td><td>This document lists the plugins that are defined through pluginManagement.</td></tr><tr class="a"><td><a href="mail-lists.html">Mailing Lists</a></td><td>This document provides subscription and archive information for this project's mailing lists.</td></tr><tr class="b"><td><a href="integration.html">Continuous Integration</a></td><td>This is a link to the definitions of all continuous integ
ration processes that builds and tests code on a frequent, regular basis.</td></tr><tr class="a"><td><a href="license.html">Project License</a></td><td>This is a link to the definitions of project licenses.</td></tr><tr class="b"><td><a href="team-list.html">Project Team</a></td><td>This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another.</td></tr><tr class="a"><td><a href="source-repository.html">Source Repository</a></td><td>This is a link to the online source repository that can be viewed via a web browser.</td></tr><tr class="b"><td><a href="index.html">About</a></td><td>The Apache WSS4J project provides a Java implementation of the primary security standards
+ for Web Services, namely the OASIS Web Services Security (WS-Security) specifications
+ from the OASIS Web Services Security TC.</td></tr><tr class="a"><td><a href="issue-tracking.html">Issue Tracking</a></td><td>This is a link to the issue management system for this project. Issues (bugs, features, change requests) can be created and queried using this link.</td></tr><tr class="b"><td><a href="project-summary.html">Project Summary</a></td><td>This document lists other related information of this project</td></tr><tr class="a"><td><a href="plugins.html">Project Plugins</a></td><td>This document lists the build plugins and the report plugins used by this project.</td></tr><tr class="b"><td><a href="dependencies.html">Dependencies</a></td><td>This document lists the project's dependencies and provides information on each dependency.</td></tr></table></div></div>
</div>
</div>
<div class="clear">
<hr/>
</div>
<div id="footer">
- <div class="xright">©
- 2004-2012
-
- The Apache Software Foundation
-
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+ Copyright © 2004-2012
+ <a href="http://www.apache.org/">The Apache Software Foundation</a>.
+ All Rights Reserved.
+
+ </div>
<div class="clear">
<hr/>
</div>
Modified: webservices/wss4j/site/project-reports.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/project-reports.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/project-reports.html (original)
+++ webservices/wss4j/site/project-reports.html Tue Dec 4 12:48:10 2012
@@ -1,17 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-
-
-
-
-
-
-
-
-
-
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 26, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Apache WSS4J - Generated Reports</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -19,202 +10,112 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- </head>
+ <meta name="Date-Revision-yyyymmdd" content="20121126" />
+ <meta http-equiv="Content-Language" content="en" />
+
+ </head>
<body class="composite">
<div id="banner">
- <a href="" id="bannerLeft">
-
- Apache WSS4J
-
- </a>
- <a href="http://www.apache.org" id="bannerRight">
-
- <img src="http://activemq.apache.org/images/asf-logo.png" alt="" />
-
- </a>
+ <a href="./" id="bannerLeft">
+ Apache WSS4J
+ </a>
+ <a href="http://www.apache.org" id="bannerRight">
+ <img src="http://activemq.apache.org/images/asf-logo.png" alt="$alt" />
+ </a>
<div class="clear">
<hr/>
</div>
</div>
<div id="breadcrumbs">
-
-
-
-
-
-
-
-
- <div class="xleft">
- Last Published: 2012-07-25
+
+
+ <div class="xleft">
+ <span id="publishDate">Last Published: 2012-11-26</span>
+ | <span id="projectVersion">Version: 1.6.8</span>
</div>
- <div class="xright">
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+
+ </div>
<div class="clear">
<hr/>
</div>
</div>
<div id="leftColumn">
<div id="navcolumn">
-
-
-
-
-
-
-
-
- <h5>Apache WSS4J</h5>
- <ul>
-
- <li class="none">
- <a href="index.html">Home</a>
- </li>
-
- <li class="none">
- <a href="download.html">Download</a>
- </li>
-
- <li class="none">
- <a href="using.html">Using WSS4J</a>
- </li>
-
- <li class="none">
- <a href="config.html">WSS4J Configuration</a>
- </li>
-
- <li class="none">
- <a href="topics.html">Special Topics</a>
- </li>
-
- <li class="none">
- <a href="wss4j16.html">WSS4J 1.6 Release Notes</a>
- </li>
+
+
+ <h5>Apache WSS4J</h5>
+ <ul>
+ <li class="none">
+ <a href="index.html" title="Home">Home</a>
+ </li>
+ <li class="none">
+ <a href="download.html" title="Download">Download</a>
+ </li>
+ <li class="none">
+ <a href="using.html" title="Using WSS4J">Using WSS4J</a>
+ </li>
+ <li class="none">
+ <a href="config.html" title="WSS4J Configuration">WSS4J Configuration</a>
+ </li>
+ <li class="none">
+ <a href="topics.html" title="Special Topics">Special Topics</a>
+ </li>
+ <li class="none">
+ <a href="best_practice.html" title="Security Best Practices">Security Best Practices</a>
+ </li>
+ <li class="none">
+ <a href="wss4j16.html" title="WSS4J 1.6 Release Notes">WSS4J 1.6 Release Notes</a>
+ </li>
</ul>
- <h5>Project Documentation</h5>
- <ul>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="collapsed">
- <a href="project-info.html">Project Information</a>
- </li>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="expanded">
- <strong>Project Reports</strong>
- <ul>
-
- <li class="none">
- <a href="dependency-analysis.html">Dependency Analysis</a>
- </li>
-
- <li class="none">
- <a href="apidocs/index.html">JavaDocs</a>
- </li>
-
- <li class="none">
- <a href="xref/index.html">Source Xref</a>
- </li>
-
- <li class="none">
- <a href="testapidocs/index.html">Test JavaDocs</a>
- </li>
-
- <li class="none">
- <a href="xref-test/index.html">Test Source Xref</a>
- </li>
+ <h5>Project Documentation</h5>
+ <ul>
+ <li class="collapsed">
+ <a href="project-info.html" title="Project Information">Project Information</a>
+ </li>
+ <li class="expanded">
+ <strong>Project Reports</strong>
+ <ul>
+ <li class="none">
+ <a href="apidocs/index.html" title="JavaDocs">JavaDocs</a>
+ </li>
+ <li class="none">
+ <a href="testapidocs/index.html" title="Test JavaDocs">Test JavaDocs</a>
+ </li>
+ <li class="none">
+ <a href="dependency-analysis.html" title="Dependency Analysis">Dependency Analysis</a>
+ </li>
+ <li class="none">
+ <a href="xref/index.html" title="Source Xref">Source Xref</a>
+ </li>
+ <li class="none">
+ <a href="xref-test/index.html" title="Test Source Xref">Test Source Xref</a>
+ </li>
</ul>
</li>
</ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
- </a>
-
-
-
-
-
-
-
-
- </div>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+ </a>
+
+
+ </div>
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Generated Reports</h2>
-<p>This document provides an overview of the various reports that are automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> Each report is briefly described below.</p>
-<div class="section"><h3>Overview</h3>
-<table class="bodyTable"><tr class="a"><th>Document</th>
-<th>Description</th>
-</tr>
-<tr class="b"><td><a href="dependency-analysis.html">Dependency Analysis</a></td>
-<td>Dependency analysis of the project (used declared, used undeclared, unused declared)</td>
-</tr>
-<tr class="a"><td><a href="apidocs/index.html">JavaDocs</a></td>
-<td>JavaDoc API documentation.</td>
-</tr>
-<tr class="b"><td><a href="xref/index.html">Source Xref</a></td>
-<td>HTML based, cross-reference version of Java source code.</td>
-</tr>
-<tr class="a"><td><a href="testapidocs/index.html">Test JavaDocs</a></td>
-<td>Test JavaDoc API documentation.</td>
-</tr>
-<tr class="b"><td><a href="xref-test/index.html">Test Source Xref</a></td>
-<td>HTML based, cross-reference version of Java test source code.</td>
-</tr>
-</table>
-</div>
-</div>
-
+ <div class="section"><h2>Generated Reports<a name="Generated_Reports"></a></h2><p>This document provides an overview of the various reports that are automatically generated by <a class="externalLink" href="http://maven.apache.org">Maven</a> . Each report is briefly described below.</p><div class="section"><h3>Overview<a name="Overview"></a></h3><table border="0" class="bodyTable"><tr class="a"><th>Document</th><th>Description</th></tr><tr class="b"><td><a href="apidocs/index.html">JavaDocs</a></td><td>JavaDoc API documentation.</td></tr><tr class="a"><td><a href="testapidocs/index.html">Test JavaDocs</a></td><td>Test JavaDoc API documentation.</td></tr><tr class="b"><td><a href="dependency-analysis.html">Dependency Analysis</a></td><td>Dependency analysis of the project (used declared, used undeclared, unused declared)</td></tr><tr class="a"><td><a href="xref/index.html">Source Xref</a></td><td>HTML based, cross-reference version of Java source code.</td></tr><tr cla
ss="b"><td><a href="xref-test/index.html">Test Source Xref</a></td><td>HTML based, cross-reference version of Java test source code.</td></tr></table></div></div>
</div>
</div>
<div class="clear">
<hr/>
</div>
<div id="footer">
- <div class="xright">©
- 2004-2012
-
- The Apache Software Foundation
-
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+ Copyright © 2004-2012
+ <a href="http://www.apache.org/">The Apache Software Foundation</a>.
+ All Rights Reserved.
+
+ </div>
<div class="clear">
<hr/>
</div>
Modified: webservices/wss4j/site/source-repository.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/source-repository.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/source-repository.html (original)
+++ webservices/wss4j/site/source-repository.html Tue Dec 4 12:48:10 2012
@@ -1,17 +1,8 @@
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
-
-
-
-
-
-
-
-
-
-
-
-<html xmlns="http://www.w3.org/1999/xhtml">
+<!-- Generated by Apache Maven Doxia Site Renderer 1.3 at Nov 26, 2012 -->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Apache WSS4J - Source Repository</title>
<style type="text/css" media="all">
@import url("./css/maven-base.css");
@@ -19,213 +10,133 @@
@import url("./css/site.css");
</style>
<link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
- <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
- </head>
+ <meta name="Date-Revision-yyyymmdd" content="20121126" />
+ <meta http-equiv="Content-Language" content="en" />
+
+ </head>
<body class="composite">
<div id="banner">
- <a href="" id="bannerLeft">
-
- Apache WSS4J
-
- </a>
- <a href="http://www.apache.org" id="bannerRight">
-
- <img src="http://activemq.apache.org/images/asf-logo.png" alt="" />
-
- </a>
+ <a href="./" id="bannerLeft">
+ Apache WSS4J
+ </a>
+ <a href="http://www.apache.org" id="bannerRight">
+ <img src="http://activemq.apache.org/images/asf-logo.png" alt="$alt" />
+ </a>
<div class="clear">
<hr/>
</div>
</div>
<div id="breadcrumbs">
-
-
-
-
-
-
-
-
- <div class="xleft">
- Last Published: 2012-07-25
+
+
+ <div class="xleft">
+ <span id="publishDate">Last Published: 2012-11-26</span>
+ | <span id="projectVersion">Version: 1.6.8</span>
</div>
- <div class="xright">
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+
+ </div>
<div class="clear">
<hr/>
</div>
</div>
<div id="leftColumn">
<div id="navcolumn">
-
-
-
-
-
-
-
-
- <h5>Apache WSS4J</h5>
- <ul>
-
- <li class="none">
- <a href="index.html">Home</a>
- </li>
-
- <li class="none">
- <a href="download.html">Download</a>
- </li>
-
- <li class="none">
- <a href="using.html">Using WSS4J</a>
- </li>
-
- <li class="none">
- <a href="config.html">WSS4J Configuration</a>
- </li>
-
- <li class="none">
- <a href="topics.html">Special Topics</a>
- </li>
-
- <li class="none">
- <a href="wss4j16.html">WSS4J 1.6 Release Notes</a>
- </li>
- </ul>
- <h5>Project Documentation</h5>
- <ul>
-
-
-
-
-
-
+
-
-
-
-
-
-
- <li class="expanded">
- <a href="project-info.html">Project Information</a>
+ <h5>Apache WSS4J</h5>
<ul>
-
- <li class="none">
- <a href="dependencies.html">Dependencies</a>
- </li>
-
- <li class="none">
- <a href="issue-tracking.html">Issue Tracking</a>
- </li>
-
- <li class="none">
- <a href="mail-lists.html">Mailing Lists</a>
- </li>
-
- <li class="none">
- <a href="license.html">Project License</a>
- </li>
-
- <li class="none">
- <strong>Source Repository</strong>
- </li>
+ <li class="none">
+ <a href="index.html" title="Home">Home</a>
+ </li>
+ <li class="none">
+ <a href="download.html" title="Download">Download</a>
+ </li>
+ <li class="none">
+ <a href="using.html" title="Using WSS4J">Using WSS4J</a>
+ </li>
+ <li class="none">
+ <a href="config.html" title="WSS4J Configuration">WSS4J Configuration</a>
+ </li>
+ <li class="none">
+ <a href="topics.html" title="Special Topics">Special Topics</a>
+ </li>
+ <li class="none">
+ <a href="best_practice.html" title="Security Best Practices">Security Best Practices</a>
+ </li>
+ <li class="none">
+ <a href="wss4j16.html" title="WSS4J 1.6 Release Notes">WSS4J 1.6 Release Notes</a>
+ </li>
+ </ul>
+ <h5>Project Documentation</h5>
+ <ul>
+ <li class="expanded">
+ <a href="project-info.html" title="Project Information">Project Information</a>
+ <ul>
+ <li class="none">
+ <a href="plugin-management.html" title="Plugin Management">Plugin Management</a>
+ </li>
+ <li class="none">
+ <a href="mail-lists.html" title="Mailing Lists">Mailing Lists</a>
+ </li>
+ <li class="none">
+ <a href="integration.html" title="Continuous Integration">Continuous Integration</a>
+ </li>
+ <li class="none">
+ <a href="license.html" title="Project License">Project License</a>
+ </li>
+ <li class="none">
+ <a href="team-list.html" title="Project Team">Project Team</a>
+ </li>
+ <li class="none">
+ <strong>Source Repository</strong>
+ </li>
+ <li class="none">
+ <a href="index.html" title="About">About</a>
+ </li>
+ <li class="none">
+ <a href="issue-tracking.html" title="Issue Tracking">Issue Tracking</a>
+ </li>
+ <li class="none">
+ <a href="project-summary.html" title="Project Summary">Project Summary</a>
+ </li>
+ <li class="none">
+ <a href="plugins.html" title="Project Plugins">Project Plugins</a>
+ </li>
+ <li class="none">
+ <a href="dependencies.html" title="Dependencies">Dependencies</a>
+ </li>
</ul>
</li>
-
-
-
-
-
-
-
-
-
-
-
-
-
- <li class="collapsed">
- <a href="project-reports.html">Project Reports</a>
- </li>
+ <li class="collapsed">
+ <a href="project-reports.html" title="Project Reports">Project Reports</a>
+ </li>
</ul>
- <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
- <img alt="Built by Maven" src="./images/logos/maven-feather.png"></img>
- </a>
-
-
-
-
-
-
-
-
- </div>
+ <a href="http://maven.apache.org/" title="Built by Maven" class="poweredBy">
+ <img class="poweredBy" alt="Built by Maven" src="./images/logos/maven-feather.png" />
+ </a>
+
+
+ </div>
</div>
<div id="bodyColumn">
<div id="contentBox">
- <div class="section"><h2>Overview</h2>
-This project uses <a class="externalLink" href="http://subversion.tigris.org/">Subversion</a> to manage its source code. Instructions on Subversion use can be found at <a class="externalLink" href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com/</a>.</div>
-<div class="section"><h2>Web Access</h2>
-<p>The following is a link to the online source repository.</p>
-<div class="source"><pre><a class="externalLink" href="http://svn.apache.org/viewvc/webservices/wss4j/trunk">http://svn.apache.org/viewvc/webservices/wss4j/trunk</a></pre>
-</div>
-</div>
-<div class="section"><h2>Anonymous access</h2>
-<p>The source can be checked out anonymously from SVN with this command:</p>
-<div class="source"><pre>$ svn checkout http://svn.apache.org/repos/asf/webservices/wss4j/trunk/ wss4j</pre>
-</div>
-</div>
-<div class="section"><h2>Developer access</h2>
-<p>Everyone can access the Subversion repository via HTTP, but Committers must checkout the Subversion repository via HTTPS.</p>
-<div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/webservices/wss4j/trunk/ wss4j</pre>
-</div>
-<p>To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)</p>
-<div class="source"><pre>$ svn commit --username your-username -m "A message"</pre>
-</div>
-</div>
-<div class="section"><h2>Access from behind a firewall</h2>
-<p>For those users who are stuck behind a corporate firewall which is blocking HTTP access to the Subversion repository, you can try to access it via the developer connection:</p>
-<div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/webservices/wss4j/trunk/ wss4j</pre>
-</div>
-</div>
-<div class="section"><h2>Access through a proxy</h2>
-<p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The file's location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)</p>
-<p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.</p>
-<p>Example: Edit the 'servers' file and add something like:</p>
-<div class="source"><pre>[global]
+ <div class="section"><h2>Overview<a name="Overview"></a></h2>This project uses <a class="externalLink" href="http://subversion.tigris.org/">Subversion</a> to manage its source code. Instructions on Subversion use can be found at <a class="externalLink" href="http://svnbook.red-bean.com/">http://svnbook.red-bean.com/</a>.</div><div class="section"><h2>Web Access<a name="Web_Access"></a></h2><p>The following is a link to the online source repository.</p><div class="source"><pre><a class="externalLink" href="http://svn.apache.org/repos/asf/webservices/wss4j/tags/1_6_8">http://svn.apache.org/repos/asf/webservices/wss4j/tags/1_6_8</a></pre></div></div><div class="section"><h2>Anonymous access<a name="Anonymous_access"></a></h2><p>The source can be checked out anonymously from SVN with this command:</p><div class="source"><pre>$ svn checkout http://svn.apache.org/repos/asf/webservices/wss4j/tags/1_6_8 wss4j</pre></div></div><div class="section"><h2>Developer access<a name=
"Developer_access"></a></h2><p>Everyone can access the Subversion repository via HTTP, but Committers must checkout the Subversion repository via HTTPS.</p><div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/webservices/wss4j/tags/1_6_8 wss4j</pre></div><p>To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)</p><div class="source"><pre>$ svn commit --username your-username -m "A message"</pre></div></div><div class="section"><h2>Access from behind a firewall<a name="Access_from_behind_a_firewall"></a></h2><p>For those users who are stuck behind a corporate firewall which is blocking HTTP access to the Subversion repository, you can try to access it via the developer connection:</p><div class="source"><pre>$ svn checkout https://svn.apache.org/repos/asf/webservices/wss4j/tags/1_6_8 wss4j</pre></div></div><div class="section"><h2>Access through a proxy<a name="Access_thr
ough_a_proxy"></a></h2><p>The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The file's location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)</p><p>There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.</p><p>Example: Edit the 'servers' file and add something like:</p><div class="source"><pre>[global]
http-proxy-host = your.proxy.name
http-proxy-port = 3128
-</pre>
-</div>
-</div>
-
+</pre></div></div>
</div>
</div>
<div class="clear">
<hr/>
</div>
<div id="footer">
- <div class="xright">©
- 2004-2012
-
- The Apache Software Foundation
-
-
-
-
-
-
-
-
- </div>
+ <div class="xright">
+ Copyright © 2004-2012
+ <a href="http://www.apache.org/">The Apache Software Foundation</a>.
+ All Rights Reserved.
+
+ </div>
<div class="clear">
<hr/>
</div>
Modified: webservices/wss4j/site/testapidocs/allclasses-frame.html
URL: http://svn.apache.org/viewvc/webservices/wss4j/site/testapidocs/allclasses-frame.html?rev=1416918&r1=1416917&r2=1416918&view=diff
==============================================================================
--- webservices/wss4j/site/testapidocs/allclasses-frame.html (original)
+++ webservices/wss4j/site/testapidocs/allclasses-frame.html Tue Dec 4 12:48:10 2012
@@ -2,13 +2,12 @@
<!--NewPage-->
<HTML>
<HEAD>
-<!-- Generated by javadoc (build 1.6.0_31) on Wed Jul 25 15:27:44 IST 2012 -->
+<!-- Generated by javadoc (build 1.5.0_22) on Mon Nov 26 14:56:52 GMT 2012 -->
<META http-equiv="Content-Type" content="text/html; charset=UTF-8">
<TITLE>
-All Classes (WSS4J 1.6.7 Test API)
+All Classes (Apache WSS4J 1.6.8 Test API)
</TITLE>
-<META NAME="date" CONTENT="2012-07-25">
<LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
@@ -64,6 +63,8 @@ All Classes (WSS4J 1.6.7 Test API)
<BR>
<A HREF="org/apache/ws/security/processor/EncryptedKeyDataRefTest.html" title="class in org.apache.ws.security.processor" target="classFrame">EncryptedKeyDataRefTest</A>
<BR>
+<A HREF="org/apache/ws/security/message/EncryptionAlgorithmSuiteTest.html" title="class in org.apache.ws.security.message" target="classFrame">EncryptionAlgorithmSuiteTest</A>
+<BR>
<A HREF="org/apache/ws/security/message/EncryptionCRLTest.html" title="class in org.apache.ws.security.message" target="classFrame">EncryptionCRLTest</A>
<BR>
<A HREF="org/apache/ws/security/message/EncryptionGCMTest.html" title="class in org.apache.ws.security.message" target="classFrame">EncryptionGCMTest</A>
@@ -102,6 +103,8 @@ All Classes (WSS4J 1.6.7 Test API)
<BR>
<A HREF="org/apache/ws/security/common/SAML2CallbackHandler.html" title="class in org.apache.ws.security.common" target="classFrame">SAML2CallbackHandler</A>
<BR>
+<A HREF="org/apache/ws/security/saml/SamlAlgorithmSuiteTest.html" title="class in org.apache.ws.security.saml" target="classFrame">SamlAlgorithmSuiteTest</A>
+<BR>
<A HREF="org/apache/ws/security/saml/SamlConditionsTest.html" title="class in org.apache.ws.security.saml" target="classFrame">SamlConditionsTest</A>
<BR>
<A HREF="org/apache/ws/security/common/SAMLElementCallbackHandler.html" title="class in org.apache.ws.security.common" target="classFrame">SAMLElementCallbackHandler</A>
@@ -126,6 +129,8 @@ All Classes (WSS4J 1.6.7 Test API)
<BR>
<A HREF="org/apache/ws/security/message/token/SecurityTokenReferenceTest.html" title="class in org.apache.ws.security.message.token" target="classFrame">SecurityTokenReferenceTest</A>
<BR>
+<A HREF="org/apache/ws/security/message/SignatureAlgorithmSuiteTest.html" title="class in org.apache.ws.security.message" target="classFrame">SignatureAlgorithmSuiteTest</A>
+<BR>
<A HREF="org/apache/ws/security/message/SignatureCertConstraintsTest.html" title="class in org.apache.ws.security.message" target="classFrame">SignatureCertConstraintsTest</A>
<BR>
<A HREF="org/apache/ws/security/message/SignatureCertTest.html" title="class in org.apache.ws.security.message" target="classFrame">SignatureCertTest</A>