[jboss-svn-commits] JBL Code SVN: r22537 - in labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured: src/org/jboss/soa/esb/samples/quickstart/webserviceproducersecured/test and 1 other directory.

[jboss-svn-commits at lists.jboss.org]

Author: beve
Date: 2008-09-09 05:25:46 -0400 (Tue, 09 Sep 2008)
New Revision: 22537

Modified:
   labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/readme.txt
   labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/src/org/jboss/soa/esb/samples/quickstart/webserviceproducersecured/test/soap_message_01.xml
Log:
Work for https://jira.jboss.org/jira/browse/JBESB-2000


Modified: labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/readme.txt
===================================================================
--- labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/readme.txt	2008-09-09 09:08:59 UTC (rev 22536)
+++ labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/readme.txt	2008-09-09 09:25:46 UTC (rev 22537)
@@ -2,8 +2,8 @@
 =========
   This sample demonstrates how to deploy a JSR181 Webservice endpoint on
   JBossESB using the SOAPProcessor action and configuring security in JBossESB.  
-  This quickstart sends a SOAP message, with a security header using a BinarySecurityToken  
-  which is a public certifcate.  
+  Authentication is done by verifying that a certificate exist in a keystore. The  
+  certifcate is identified by an alias and a keyPassword which is configured in jboss-esb.xml
 
 Running this quickstart:
 ========================
@@ -17,7 +17,33 @@
 To Run:
 =======
   1. Type 'ant deploy'.
-  2. Restart you esb server
+  2. Restart you esb server
   2. Type 'ant runtest'.
   3. Switch back to Application Server console to see the output from the ESB
   4. In this folder ("Window1"), type 'ant undeploy'.
+
+Things to look for in this quickstart:
+======================================
+  1. Security configuration in jboss-esb.xml:
+	<security moduleName="CertLogin" runAs="adminRole" callbackHandler="org.jboss.internal.soa.esb.services.security.CertCallbackHandler">
+		<property name="alias" value="jbossesb"/>
+		<property name="keyPassword" value="jbossesb"/>
+	</security>
+	In the above configuration the 'alias' specifies a alias that will be used to identify a certificate in the keystore.	
+	The 'keyPassword' is the password for the certificate.
+	Try updating either the alias of the password to trigger an authentication failure.
+
+  2. jaas.login:
+	 CertLogin {
+			com.sun.security.auth.module.KeyStoreLoginModule required keyStoreURL="file://@KEYSTORE_PATH@" debug=false;
+	 };
+	 This file contains the JAAS login module configuration. As you can see the keyStoreURL points to the keystore
+	 to use. This file gets filtered and the path is set in build.xml.
+
+  
+
+
+
+ 	 	
+
+

Modified: labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/src/org/jboss/soa/esb/samples/quickstart/webserviceproducersecured/test/soap_message_01.xml
===================================================================
--- labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/src/org/jboss/soa/esb/samples/quickstart/webserviceproducersecured/test/soap_message_01.xml	2008-09-09 09:08:59 UTC (rev 22536)
+++ labs/jbossesb/branches/JBESB_4_4_GA_CP/product/samples/quickstarts/webservice_producer_secured/src/org/jboss/soa/esb/samples/quickstart/webserviceproducersecured/test/soap_message_01.xml	2008-09-09 09:25:46 UTC (rev 22537)
@@ -1,18 +1,5 @@
 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:good="http://webservice_producer/goodbyeworld">
    <soapenv:Header>
-<wsse:Security xmlns:wsse="http://schemas.xmlsoap.org/ws/2002/04/secext">
-            <wsse:BinarySecurityToken EncodingType="wsse:Base64Binary" ValueType="wsse:X509v3">MIICVDCCAb0CBEii4NgwDQYJKoZIhvcNAQEEBQAwcTELMAkGA1UEBhMCU0UxEjAQBgNVBAgTCVN0
-b2NraG9sbTESMBAGA1UEBxMJU3RvY2tob2xtMRAwDgYDVQQKEwdSZWQgSGF0MQ4wDAYDVQQLEwVK
-Qm9zczEYMBYGA1UEAxMPRGFuaWVsIEJldmVuaXVzMB4XDTA4MDgxMzEzMjU0NFoXDTM1MTIyOTEz
-MjU0NFowcTELMAkGA1UEBhMCU0UxEjAQBgNVBAgTCVN0b2NraG9sbTESMBAGA1UEBxMJU3RvY2to
-b2xtMRAwDgYDVQQKEwdSZWQgSGF0MQ4wDAYDVQQLEwVKQm9zczEYMBYGA1UEAxMPRGFuaWVsIEJl
-dmVuaXVzMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCJRSE6wHkF5DK6DkHTMPnP4dNZXeon
-cCP7Ufn5hjXWLdsq9dAEbuiRLAE4HoNxxqgCHdoKjMO9N1/CIn5dmWw4DBWLp8OHx8Wnyp0MYmCz
-B31jHJpuXkkRq50vRYtKN0NIOyw7eF+XWf4u0dXNgFtXHuUxhAyEm/kTxO1SNVUTwwIDAQABMA0G
-CSqGSIb3DQEBBAUAA4GBADCzl0gXAY0xysdHkKNdwaBDzlibLPz2zmaHcit841qVn05p/I1gsbUV
-vEPh6i/Dj57vdE+X66sPbI36uZiqyWqEr6wvCJDtaTbhSLmckk7ioXwLvdKEQ150MPBsjWRRnFGN
-tZhrQfjo0q8seLh0kgconbfN4pHllfNkJPcdSBvi</wsse:BinarySecurityToken>
-        </wsse:Security>
    </soapenv:Header>
    <soapenv:Body>
       <good:sayGoodbye>