[jboss-svn-commits] JBL Code SVN: r29320 - labs/jbossesb/workspace/dbevenius/saml_support/product/samples/quickstarts/security_saml.

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

Author: beve
Date: 2009-09-14 03:34:46 -0400 (Mon, 14 Sep 2009)
New Revision: 29320

Modified:
   labs/jbossesb/workspace/dbevenius/saml_support/product/samples/quickstarts/security_saml/readme.txt
Log:
Minor update.


Modified: labs/jbossesb/workspace/dbevenius/saml_support/product/samples/quickstarts/security_saml/readme.txt
===================================================================
--- labs/jbossesb/workspace/dbevenius/saml_support/product/samples/quickstarts/security_saml/readme.txt	2009-09-14 01:22:10 UTC (rev 29319)
+++ labs/jbossesb/workspace/dbevenius/saml_support/product/samples/quickstarts/security_saml/readme.txt	2009-09-14 07:34:46 UTC (rev 29320)
@@ -1,13 +1,18 @@
 Overview:
 =========
   This quickstart demonstrates JBossESB support for SAML. The SAML support is provided by 
-  JBoss Security Token Service (JBossSTS).
+  using JBoss Security Token Service (JBossSTS).
 
+
   The following will be demonstrated by this quickstart:
 	* Configuring a service to use JBossSTSLoginModule to validate a SAML Assertion.
-	* Calling WS gateway with a SAML Assertion previously requested from JBossSTS
+	  In JBossESB a service may be configured to use the JBossSTSLoginModule. This JAAS Login Module
+	  expects the caller to have a SAML Assertion in its AuthenticationRequest. 
 
 	* Using the JBossSTSAction to request a SAML Assertion from JBossSTS
+	  This action would be used when a call to one or more internal or external
+	  service require a valid SAML Assertion. This would be called once and authentication
+	  would only be performed once.
 
 Running this quickstart:
 ========================
@@ -17,39 +22,12 @@
 To Run:
 ===========================
   1. Type 'ant deploy'.
-  1. Copy+Paste the contents of ./login-config.xml *into* <server>/<configname>/conf/login-config.xml
-  2. Deploy jboss-sts.war to the application server by copying it into the deploy directory.
-  3. Start the server.
+  2. Copy+Paste the contents of *build*/login-config.xml *into* <server>/<configname>/conf/login-config.xml
+  3. Deploy jboss-sts.war to the application server by copying it into the deploy directory.
+  4. Start the server.
   5. 'ant runtest' will send a HTTP request to a JBossRemoting Gatway
   6. 'ant sendesb' will invoke the Service directly using the ServiceInvoker
 
-What to look for in this quickstart
-===================================
-  # Security configuration
-	 <service category="Security" name="SimpleListenerSecured" description="Hello World">
-            <security moduleName="jbossesb" rolesAllowed="esbrole"/>
-	The security element declares that this service requires authentication to be executed and that the 
-	authenticated users be a member in the role 'esbrole'. The role is determined by the JAAS login
-	module being used, in this case by the 'jbossesb' module specified in login-config.xml.
-
-  # src/org/jboss/soa/esb/samples/quickstart/securitybasic/test/HttpClient.java
-	This is a JBossRemoting client that uses http to invoke the JBossRemoting gateway.
-
-  # src/org/jboss/soa/esb/samples/quickstart/securitybasic/test/SendEsbMessage.java 
-	This class uses the ServiceInvoker to invoke the ESB service directly, by-passing the gateway.
-	You can see how an AuthenticationRequest is created then encrypted, and passed to the ESB
-	by attaching the authentication request to the ESB Message object.
-
-  # src/org/jboss/soa/esb/samples/quickstart/securitybasic/MyListenerAction.java 
-	This ESB Action show how the currently autenticated JAAS Subject can be accessed:
-	System.out.println("Subject in MyListenerAction : " + Subject.getSubject(AccessController.getContext()));
-
-  # esb-users-properties
-	User/password configuration.
-
-  # esb-roles.properties
-	Roles/users configuration.
-	
   # Please refer to the "Security" section of the ServiceGuide.pdf for more details on the security features of JBossESB.