[jboss-cvs] JBossAS SVN: r64373 - projects/security/security-spi/trunk/src/main/org/jboss/security.

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

Author: anil.saldhana at jboss.com
Date: 2007-07-31 14:02:12 -0400 (Tue, 31 Jul 2007)
New Revision: 64373

Modified:
   projects/security/security-spi/trunk/src/main/org/jboss/security/AuthenticationManager.java
Log:
Add a new method for JASPI

Modified: projects/security/security-spi/trunk/src/main/org/jboss/security/AuthenticationManager.java
===================================================================
--- projects/security/security-spi/trunk/src/main/org/jboss/security/AuthenticationManager.java	2007-07-31 18:01:45 UTC (rev 64372)
+++ projects/security/security-spi/trunk/src/main/org/jboss/security/AuthenticationManager.java	2007-07-31 18:02:12 UTC (rev 64373)
@@ -25,6 +25,7 @@
 import java.util.Map;
 
 import javax.security.auth.Subject;
+import javax.security.auth.message.MessageInfo;
 
 /** The AuthenticationManager is responsible for validating credentials
  * associated with principals.
@@ -74,6 +75,15 @@
    */
    boolean isValid(Principal principal, Object credential,
       Subject activeSubject);
+   
+   /**
+    * Authenticate a Subject given the request response JSR-196(JASPI) messages
+    * @param requestMessage 
+    * @param clientSubject Pre-created or null subject
+    * @param layer Message Layer for the JASPI (Optional):  Default: HTTP
+    * @return true if client subject is valid, false otherwise
+    */
+   boolean isValid(MessageInfo requestMessage, Subject clientSubject, String layer);
 
    /** Get the currently authenticated subject. Historically implementations of
     AuthenticationManager isValid methods had the side-effect of setting the