Author: alessio.soldano(a)jboss.com
Date: 2007-10-29 05:39:25 -0400 (Mon, 29 Oct 2007)
New Revision: 4906
Modified:
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/SignTestCase.java
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/UsernameTokenHTTPSTestCase.java
Log:
Doc
Modified:
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/SignTestCase.java
===================================================================
---
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/SignTestCase.java 2007-10-27
17:32:13 UTC (rev 4905)
+++
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/SignTestCase.java 2007-10-29
09:39:25 UTC (rev 4906)
@@ -31,7 +31,7 @@
/**
* WCF Interoperability Plug-fest - November 2007
*
- * Scenario 3.2:
+ * Scenario 3.2: X509 Mutual Authentication, Sign Only
*
* Client and Server are authenticated and messages integrity are provided by using
Asymmetric Binding
* from Security Policy with server X509 certificate used as Recepient Token and client
X509 certificate
@@ -50,7 +50,7 @@
*
* @author Alessio Soldano <alessio.soldano(a)jboss.com>
*
- * @version $Id:$
+ * @version $Id$
* @since 27-Oct-2007
*/
public class SignTestCase extends AbstractWSSEBase
Modified:
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/UsernameTokenHTTPSTestCase.java
===================================================================
---
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/UsernameTokenHTTPSTestCase.java 2007-10-27
17:32:13 UTC (rev 4905)
+++
stack/native/branches/asoldano/trunk/src/test/java/org/jboss/test/ws/interop/nov2007/wsse/UsernameTokenHTTPSTestCase.java 2007-10-29
09:39:25 UTC (rev 4906)
@@ -32,7 +32,7 @@
/**
* WCF Interoperability Plug-fest - November 2007
*
- * Scenario 3.1:
+ * Scenario 3.1: Username token Auth with HTTPS protection
* Client authenticates by passing UsernameToken in Request. Request and Response are
protected by HTTPS.
* SOAP Version: 1.1
* Addressing: No