diff --git a/tck-dist/userguide/src/main/jbake/content/config.inc b/tck-dist/userguide/src/main/jbake/content/config.inc index 4bb6f36..3caa744 100644 --- a/tck-dist/userguide/src/main/jbake/content/config.inc +++ b/tck-dist/userguide/src/main/jbake/content/config.inc @@ -49,19 +49,32 @@ and configuration to support your implementation and Arqulillian container imple starts up your container and deploys the test wars into it. -4.3 Setting up an Evironment Against a Jakarta EE {JakartaEEVersion} CI for legacy TCK tests +4.3 Setting up an Evironment Against a Jakarta EE {JakartaEEVersion} CI for SPI TCK tests ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The legacy tests which are part of the latest Jakarta Authentication TCK use `KEYWORDS` parameter to identify the -tests that need to be executed for JakartaEE Full and Web profile implementations. The tck/old-tck/run/pom.xml includes -example of using the profiles `platform` (for JakartaEE Platform - Full profile by default) and `web` (for Web Profile) -that sets the appropirate values for `KEYWORDS` in the CI. +The SPI tests (in [tck]/spi which are part of the latest Jakarta Authentication TCK need additional configuration. -``` -For JakartaEE Platform Full profile , KEYWORDS = jaspic_baseline|javaee -For JakartaEE Platform Web platform , KEYWORDS = jaspic_web_profile -``` +These SPI tests dive a little deeper into the assertions of the Jakarta Authentication SPI, and directly test for a number of +technical expectations. In contrast, most other tests in the Jakarta Authentication TCK look more at observable system +behavior and are more akin to Integration Tests (IT). + +The common sub-module ([tck]/spi/module) of the SPI module primarily contains a special AuthConfigFactory (the TSSV) that is installed +using a ServletContainerInitializer. This AuthConfigFactory traces a lot of operations +on it to a logging file (saved to location set by system property "log.file.location"). +This logging file is read by the (client side) tests, which verify whether specific entries are present or absent in said log file. + +Both the CI (e.g. Eclipse GlassFish) and the client environment running the tests (junit) needs to have this "log.file.location" specified and +pointing to the same location. + +Among the SPI tests is a test for the "auth context ID", which can be obtained in a standard way, but contains an implementation specific +value. In order to test that this value is correct, the expected value for a CI needs to be configured using the client environment +system property "logical.hostname.servlet". + +A Jakarta Authentication implementation provides an "AuthConfigFactory" implementation, which can be obtained in a standard way, but +obviously is of a implementation specific type. In order to test various assumptions about this "vendor AuthConfigFactory", the exact type +needs to be provided to the tests via the system property "vendor.authconfig.factory". Both the CI (e.g. GlassFish) and the client +environment running the tests (junit) needs to have this "vendor.authconfig.factory" specified and set to the same value. -The `tck/old-tck/source/src/com/sun/ts/lib/harness/keyword.properties` has the full list of keywords -mapped to the test directories in tck/old-tck/ +The `tck/pom.xml` file contains a full example for Eclipse GlassFish in the "glassfish-ci-managed" profile in the surefire configuration +section. diff --git a/tck-dist/userguide/src/main/jbake/content/toc.adoc b/tck-dist/userguide/src/main/jbake/content/toc.adoc index 93b2d97..55b3346 100644 --- a/tck-dist/userguide/src/main/jbake/content/toc.adoc +++ b/tck-dist/userguide/src/main/jbake/content/toc.adoc @@ -71,7 +71,7 @@ link:using.html#GBFWO[5 Executing Tests] ** link:using.html#GBFWM[5.2 Running a Subset of the Tests] *** link:using.html#GBFWK[5.2.1 To Run a Subset of Tests in Command-Line Mode] ** link:using.html#GCLRR[5.3 Running the TCK Against GlassFish] -** link:using.html#GDMSS[5.4 Running the Legacy TCK tests Against GlassFish] + [[debugging-test-problems]] link:debug.html#GBFUV[6 Debugging Test Problems] diff --git a/tck-dist/userguide/src/main/jbake/content/using.adoc b/tck-dist/userguide/src/main/jbake/content/using.adoc index 3a6df01..f4ddbea 100644 --- a/tck-dist/userguide/src/main/jbake/content/using.adoc +++ b/tck-dist/userguide/src/main/jbake/content/using.adoc @@ -102,27 +102,10 @@ The tests in the directory are run. All the tests can be run against GlassFish by invoking the following from the tck/ directory: -`mvn clean verify`. This will include the legacy -TCK JavaTest based tests in tck/old-tck. +`mvn clean verify`. [[GDMSS]][[running-the-tck-against-the-glassfish]] -5.4 Running the Legacy TCK tests Against GlassFish -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - -The legacy JavaTest based TCK tests are in tck/old-tck folder. -They can be run by below: - -1. Change to the directory tck/old-tck. -2. Start the test run by executing the following command: + -+ -[source] ----- -mvn clean verify ----- -+ -The legacy JavaTest based TCK tests in the directory are run. - include::using.inc[] diff --git a/tck/spi/JavadocAssertions.html b/tck/spi/JavadocAssertions.html new file mode 100644 index 0000000..d0973d4 --- /dev/null +++ b/tck/spi/JavadocAssertions.html @@ -0,0 +1,1569 @@ + + + + + +JavaDoc Assertion Detail + + +
+
+

+ Jakarta Authentication - 3.1.0
JavaDoc Assertion Detail +

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
TotalsTotalActiveDeprecatedRemoved
# of Assertions 10710700
# of Required Assertions 10710700
# of Optional Assertions 0000
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
IDReturnMethod/FieldDescriptionRequiredDeprecatedTestable
JASPIC:JAVADOC:1AuthExceptionjakarta.security.auth.message.AuthException.AuthException
+ 		Constructs an AuthException with no detail + message. A detail message is a String that describes this particular exception. true
+ 		true
JASPIC:JAVADOC:2AuthExceptionjakarta.security.auth.message.AuthException.AuthException
+ + ( String ) + 		Constructs an AuthException with the + specified detail message. A detail message is a String that describes this particular exception. true
+ 		true
JASPIC:JAVADOC:3voidjakarta.security.auth.message.ClientAuth.cleanSubject
+ + ( MessageInfo ,
Subject ) + 		Remove implementation specific principals and + credentials from the subject. true
+ 		true
JASPIC:JAVADOC:4voidjakarta.security.auth.message.ClientAuth.cleanSubject
+ + ( MessageInfo ,
Subject )
throws AuthException
+ 		If an error occurs during the Subject + processing.true
+ 		true
JASPIC:JAVADOC:5AuthStatusjakarta.security.auth.message.ClientAuth.secureRequest
+ + ( MessageInfo ,
Subject ) + 		Secure a service request message before + sending it to the service. This method is called to transform the request message acquired by + calling getRequestMessage (on messageInfo) into the mechanism-specific form to be sent by the + runtime. This method conveys the outcome of its message processing either by returning an AuthStatus + value or by throwing an AuthException. true
+ 		true
JASPIC:JAVADOC:6AuthStatusjakarta.security.auth.message.ClientAuth.secureRequest
+ + ( MessageInfo ,
Subject )
throws AuthException
+ 		When the message processing failed without + establishing a failure response message (in messageInfo).true
+ 		true
JASPIC:JAVADOC:7AuthStatusjakarta.security.auth.message.ClientAuth.validateResponse
+ + ( MessageInfo ,
Subject ,
Subject ) + 		Validate a received service response. This + method is called to transform the mechanism-specific response message acquired by calling + getResponseMessage (on messageInfo) into the validated application message to be returned to the + message processing runtime. If the response message is a (mechanism-specific) meta-message, the + method implementation must attempt to transform the meta-message into the next mechanism-specific + request message to be sent by the runtime. This method conveys the outcome of its message processing + either by returning an AuthStatus value or by throwing an AuthException. true
+ 		true
JASPIC:JAVADOC:8AuthStatusjakarta.security.auth.message.ClientAuth.validateResponse
+ + ( MessageInfo ,
Subject ,
Subject )
throws AuthException
+ 		When the message processing failed without + establishing a failure response message (in messageInfo).true
+ 		true
JASPIC:JAVADOC:9Mapjakarta.security.auth.message.MessageInfo.getMap
+ 		Get (a reference to) the Map object of this + MessageInfo. Operations performed on the acquired Map must effect the Map within the MessageInfo. true
+ 		true
JASPIC:JAVADOC:10Objectjakarta.security.auth.message.MessageInfo.getRequestMessage
+ 		Get the request message object from this + MessageInfo. true
+ 		true
JASPIC:JAVADOC:11Objectjakarta.security.auth.message.MessageInfo.getResponseMessage
+ 		Get the response message object from this + MessageInfo. true
+ 		true
JASPIC:JAVADOC:12voidjakarta.security.auth.message.MessageInfo.setRequestMessage
+ + ( Object ) + 		Set the request message object in this + MessageInfo. true
+ 		true
JASPIC:JAVADOC:13voidjakarta.security.auth.message.MessageInfo.setResponseMessage
+ + ( Object ) + 		Set the response message object in this + MessageInfo. true
+ 		true
JASPIC:JAVADOC:14TargetPolicy[]jakarta.security.auth.message.MessagePolicy.getTargetPolicies
+ 		Get the target policies that comprise the + authentication policy. true
+ 		true
JASPIC:JAVADOC:15booleanjakarta.security.auth.message.MessagePolicy.isMandatory
+ 		Get the MessagePolicy modifier. true
+ 		true
JASPIC:JAVADOC:16MessagePolicyjakarta.security.auth.message.MessagePolicy.MessagePolicy
+ + ( TargetPolicy[] ,
boolean ) + 		Create a MessagePolicy instance with an array + of target policies. true
+ 		true
JASPIC:JAVADOC:17Stringjakarta.security.auth.message.MessagePolicy.ProtectionPolicy.getID
+ 		Get the ProtectionPolicy identifier. An + identifier may represent a conceptual protection policy (as is the case with the static identifiers + defined within this interface) or it may identify a procedural policy expression or plan that may be + more difficult to categorize in terms of a conceptual identifier. true
+ 		true
JASPIC:JAVADOC:18Objectjakarta.security.auth.message.MessagePolicy.Target.get
+ + ( MessageInfo ) + 		Get the Object identified by the Target from + the MessageInfo. true
+ 		true
JASPIC:JAVADOC:19voidjakarta.security.auth.message.MessagePolicy.Target.put
+ + ( MessageInfo ,
Object ) + 		Put the Object into the MessageInfo at the + location identified by the target. true
+ 		true
JASPIC:JAVADOC:20voidjakarta.security.auth.message.MessagePolicy.Target.remove
+ + ( MessageInfo ) + 		Remove the Object identified by the Target + from the MessageInfo. true
+ 		true
JASPIC:JAVADOC:21ProtectionPolicyjakarta.security.auth.message.MessagePolicy.TargetPolicy.getProtectionPolicy
+ 		Get the ProtectionPolicy that applies to the + targets. true
+ 		true
JASPIC:JAVADOC:22Target[]jakarta.security.auth.message.MessagePolicy.TargetPolicy.getTargets
+ 		Get the array of layer-specific target + descriptors that identify the one or more message parts to which the specified message protection + policy applies. true
+ 		true
JASPIC:JAVADOC:23TargetPolicyjakarta.security.auth.message.MessagePolicy.TargetPolicy.MessagePolicy.TargetPolicy
+ + ( Target[] ,
ProtectionPolicy ) + 		Create a TargetPolicy instance with an array + of Targets and with a ProtectionPolicy. true
+ 		true
JASPIC:JAVADOC:24voidjakarta.security.auth.message.ServerAuth.cleanSubject
+ + ( MessageInfo ,
Subject ) + 		Remove method specific principals and + credentials from the subject. true
+ 		true
JASPIC:JAVADOC:25voidjakarta.security.auth.message.ServerAuth.cleanSubject
+ + ( MessageInfo ,
Subject )
throws AuthException
+ 		If an error occurs during the Subject + processing.true
+ 		true
JASPIC:JAVADOC:26AuthStatusjakarta.security.auth.message.ServerAuth.secureResponse
+ + ( MessageInfo ,
Subject ) + 		Secure a service response before sending it + to the client. This method is called to transform the response message acquired by calling + getResponseMessage (on messageInfo) into the mechanism-specific form to be sent by the runtime. This + method conveys the outcome of its message processing either by returning an AuthStatus value or by + throwing an AuthException. true
+ 		true
JASPIC:JAVADOC:27AuthStatusjakarta.security.auth.message.ServerAuth.secureResponse
+ + ( MessageInfo ,
Subject )
throws AuthException
+ 		When the message processing failed without + establishing a failure response message (in messageInfo).true
+ 		true
JASPIC:JAVADOC:28AuthStatusjakarta.security.auth.message.ServerAuth.validateRequest
+ + ( MessageInfo ,
Subject ,
Subject ) + 		Authenticate a received service request. This + method is called to transform the mechanism-specific request message acquired by calling + getRequestMessage (on messageInfo) into the validated application message to be returned to the + message processing runtime. If the received message is a (mechanism-specific) meta-message, the + method implementation must attempt to transform the meta-message into a corresponding + mechanism-specific response message, or to the validated application request message. The runtime + will bind a validated application message into the the corresponding service invocation. This method + conveys the outcome of its message processing either by returning an AuthStatus value or by throwing + an AuthException. true
+ 		true
JASPIC:JAVADOC:29AuthStatusjakarta.security.auth.message.ServerAuth.validateRequest
+ + ( MessageInfo ,
Subject ,
Subject )
throws AuthException
+ 		When the message processing failed without + establishing a failure response message (in messageInfo).true
+ 		true
JASPIC:JAVADOC:30CallerPrincipalCallbackjakarta.security.auth.message.callback.CallerPrincipalCallback.CallerPrincipalCallback
+ + ( Subject ,
Principal ) + 		Create a CallerPrincipalCallback to set the + container's representation of the caller principal true
+ 		true
JASPIC:JAVADOC:31CallerPrincipalCallbackjakarta.security.auth.message.callback.CallerPrincipalCallback.CallerPrincipalCallback
+ + ( Subject ,
String ) + 		Create a CallerPrincipalCallback to set the + container's representation of the caller principal. true
+ 		true
JASPIC:JAVADOC:32Stringjakarta.security.auth.message.callback.CallerPrincipalCallback.getName
+ 		Get the caller principal name. true
+ 		true
JASPIC:JAVADOC:33Principaljakarta.security.auth.message.callback.CallerPrincipalCallback.getPrincipal
+ 		Get the caller principal. true
+ 		true
JASPIC:JAVADOC:34Subjectjakarta.security.auth.message.callback.CallerPrincipalCallback.getSubject
+ 		Get the Subject in which the handler will + distinguish the caller principal true
+ 		true
JASPIC:JAVADOC:35CertStoreCallbackjakarta.security.auth.message.callback.CertStoreCallback.CertStoreCallback
+ 		Create a CertStoreCallback. true
+ 		true
JASPIC:JAVADOC:36CertStorejakarta.security.auth.message.callback.CertStoreCallback.getCertStore
+ 		Used by the CertStore user to obtain the + CertStore set within the Callback. true
+ 		true
JASPIC:JAVADOC:37voidjakarta.security.auth.message.callback.CertStoreCallback.setCertStore
+ + ( CertStore ) + 		Used by the CallbackHandler to set the + CertStore within the Callback. true
+ 		true
JASPIC:JAVADOC:38String[]jakarta.security.auth.message.callback.GroupPrincipalCallback.getGroups
+ 		Get the array of group names. true
+ 		true
JASPIC:JAVADOC:39Subjectjakarta.security.auth.message.callback.GroupPrincipalCallback.getSubject
+ 		Get the Subject in which the handler will + establish the group principals. true
+ 		true
JASPIC:JAVADOC:40GroupPrincipalCallbackjakarta.security.auth.message.callback.GroupPrincipalCallback.GroupPrincipalCallback
+ + ( Subject ,
String[] ) + 		Create a GroupPrincipalCallback to establish + the container's representation of the corresponding group principals within the Subject. true
+ 		true
JASPIC:JAVADOC:41voidjakarta.security.auth.message.callback.PasswordValidationCallback.clearPassword
+ 		Clear the password. true
+ 		true
JASPIC:JAVADOC:42char[]jakarta.security.auth.message.callback.PasswordValidationCallback.getPassword
+ 		Get the password. Note that this method + returns a reference to the password. If a clone of the array is created it is the caller's + responsibility to zero out the password information after it is no longer needed. true
+ 		true
JASPIC:JAVADOC:43booleanjakarta.security.auth.message.callback.PasswordValidationCallback.getResult
+ 		Get the authentication result. true
+ 		true
JASPIC:JAVADOC:44Subjectjakarta.security.auth.message.callback.PasswordValidationCallback.getSubject
+ 		Get the subject. true
+ 		true
JASPIC:JAVADOC:45Stringjakarta.security.auth.message.callback.PasswordValidationCallback.getUsername
+ 		Get the username. true
+ 		true
JASPIC:JAVADOC:46PasswordValidationCallbackjakarta.security.auth.message.callback.PasswordValidationCallback.PasswordValidationCallback
+ + ( Subject ,
String ,
char[] ) + 		Create a PasswordValidationCallback. true
+ 		true
JASPIC:JAVADOC:47voidjakarta.security.auth.message.callback.PasswordValidationCallback.setResult
+ + ( boolean ) + 		Set the authentication result. true
+ 		true
JASPIC:JAVADOC:48Certificate[]jakarta.security.auth.message.callback.PrivateKeyCallback.getChain
+ 		Used to obtain the certicicate chain set + within the Callback. true
+ 		true
JASPIC:JAVADOC:49PrivateKeyjakarta.security.auth.message.callback.PrivateKeyCallback.getKey
+ 		Used to obtain the private key set within the + Callback. true
+ 		true
JASPIC:JAVADOC:50Requestjakarta.security.auth.message.callback.PrivateKeyCallback.getRequest
+ 		Used by the CallbackHandler to get the + Request object that identifies the private key to be returned. true
+ 		true
JASPIC:JAVADOC:51PrivateKeyCallbackjakarta.security.auth.message.callback.PrivateKeyCallback.PrivateKeyCallback
+ + ( Request ) + 		Constructs this PrivateKeyCallback with a + private key Request object. The request object identifies the private key to be returned. The + corresponding certificate chain for the private key is also returned. If the request object is null, + the handler of the callback relies on its own default. true
+ 		true
JASPIC:JAVADOC:52voidjakarta.security.auth.message.callback.PrivateKeyCallback.setKey
+ + ( PrivateKey ,
Certificate[] ) + 		Used by the CallbackHandler to set the + requested private key and the corresponding certificate chain within the Callback. If the requested + private key or chain could not be found, then both values must be set to null. true
+ 		true
JASPIC:JAVADOC:53Stringjakarta.security.auth.message.callback.PrivateKeyCallback.AliasRequest.getAlias
+ 		Get the alias. true
+ 		true
JASPIC:JAVADOC:54AliasRequestjakarta.security.auth.message.callback.PrivateKeyCallback.AliasRequest.PrivateKeyCallback.AliasRequest
+ + ( String ) + 		Construct an AliasRequest with an alias. The + alias is used to directly identify the private key to be returned. The corresponding certificate + chain for the private key is also returned. If the alias is null, the handler of the callback relies + on its own default. true
+ 		true
JASPIC:JAVADOC:55Stringjakarta.security.auth.message.callback.PrivateKeyCallback.DigestRequest.getAlgorithm
+ 		Get the algorithm identifier. true
+ 		true
JASPIC:JAVADOC:56byte[]jakarta.security.auth.message.callback.PrivateKeyCallback.DigestRequest.getDigest
+ 		Get the digest value. true
+ 		true
JASPIC:JAVADOC:57DigestRequestjakarta.security.auth.message.callback.PrivateKeyCallback.DigestRequest.PrivateKeyCallback.DigestRequest
+ + ( byte[] ,
String ) + 		Constructs a DigestRequest with a digest + value and algorithm identifier. The digest of the certificate whose private key is returned must + match the provided digest. The certificate digest is computed by applying the specified algorithm to + the bytes of the certificate. For example: + MessageDigest.getInstance(algorithm).digest(cert.getEncoded()) . The corresponding certificate chain + for the private key is also returned. If the digest or algorithm parameters are null, the handler of + the callback relies on its own defaults. true
+ 		true
JASPIC:JAVADOC:58X500Principaljakarta.security.auth.message.callback.PrivateKeyCallback.IssuerSerialNumRequest.getIssuer
+ 		Get the issuer. true
+ 		true
JASPIC:JAVADOC:59BigIntegerjakarta.security.auth.message.callback.PrivateKeyCallback.IssuerSerialNumRequest.getSerialNum
+ 		Get the serial number. true
+ 		true
JASPIC:JAVADOC:60IssuerSerialNumRequestjakarta.security.auth.message.callback.PrivateKeyCallback.IssuerSerialNumRequest.PrivateKeyCallback.IssuerSerialNumRequest
+ + ( X500Principal ,
BigInteger ) + 		Constructs a IssuerSerialNumRequest with an + issuer/serial number. The issuer/serial number is used to identify a public key certificate. The + corresponding private key is returned in the callback. The corresponding certificate chain for the + private key is also returned. If the issuer/serialNumber parameters are null, the handler of the + callback relies on its own defaults. true
+ 		true
JASPIC:JAVADOC:61byte[]jakarta.security.auth.message.callback.PrivateKeyCallback.SubjectKeyIDRequest.getSubjectKeyID
+ 		Get the subjectKeyID. true
+ 		true
JASPIC:JAVADOC:62SubjectKeyIDRequestjakarta.security.auth.message.callback.PrivateKeyCallback.SubjectKeyIDRequest.PrivateKeyCallback.SubjectKeyIDRequest
+ + ( byte[] ) + 		Construct a SubjectKeyIDRequest with an + subjectKeyID. The subjectKeyID is used to directly identify the private key to be returned. The + corresponding certificate chain for the private key is also returned. If the subjectKeyID is null, + the handler of the callback relies on its own default. true
+ 		true
JASPIC:JAVADOC:63SecretKeyjakarta.security.auth.message.callback.SecretKeyCallback.getKey
+ 		Used to obtain the secret key set within the + Callback. true
+ 		true
JASPIC:JAVADOC:64Requestjakarta.security.auth.message.callback.SecretKeyCallback.getRequest
+ 		Used by the CallbackHandler to get the + Request object which identifies the secret key to be returned. true
+ 		true
JASPIC:JAVADOC:65SecretKeyCallbackjakarta.security.auth.message.callback.SecretKeyCallback.SecretKeyCallback
+ + ( Request ) + 		Constructs this SecretKeyCallback with a + secret key Request object. The request object identifies the secret key to be returned. If the alias + is null, the handler of the callback relies on its own default. true
+ 		true
JASPIC:JAVADOC:66voidjakarta.security.auth.message.callback.SecretKeyCallback.setKey
+ + ( SecretKey ) + 		Used by the CallbackHandler to set the + requested secret key within the Callback. true
+ 		true
JASPIC:JAVADOC:67Stringjakarta.security.auth.message.callback.SecretKeyCallback.AliasRequest.getAlias
+ 		Get the alias. true
+ 		true
JASPIC:JAVADOC:68AliasRequestjakarta.security.auth.message.callback.SecretKeyCallback.AliasRequest.SecretKeyCallback.AliasRequest
+ + ( String ) + 		Construct an AliasRequest with an alias. The + alias is used to directly identify the secret key to be returned. If the alias is null, the handler + of the callback relies on its own default. true
+ 		true
JASPIC:JAVADOC:69KeyStorejakarta.security.auth.message.callback.TrustStoreCallback.getTrustStore
+ 		Used by the TrustStore user to obtain the + TrustStore set within the Callback. true
+ 		true
JASPIC:JAVADOC:70voidjakarta.security.auth.message.callback.TrustStoreCallback.setTrustStore
+ + ( KeyStore ) + 		Used by the CallbackHandler to set the + trusted certificate keystore within the Callback. true
+ 		true
JASPIC:JAVADOC:71TrustStoreCallbackjakarta.security.auth.message.callback.TrustStoreCallback.TrustStoreCallback
+ 		Create a TrustStoreCallback. true
+ 		true
JASPIC:JAVADOC:72Stringjakarta.security.auth.message.config.AuthConfig.getAppContext
+ 		Get the application context identifier of + this authentication context configuration object. true
+ 		true
JASPIC:JAVADOC:73Stringjakarta.security.auth.message.config.AuthConfig.getAuthContextID
+ + ( MessageInfo ) + 		Get the authentication context identifier + corresponding to the request and response objects encapsulated in messageInfo. true
+ 		true
JASPIC:JAVADOC:74Stringjakarta.security.auth.message.config.AuthConfig.getMessageLayer
+ 		Get the message layer name of this + authentication context configuration object. true
+ 		true
JASPIC:JAVADOC:75booleanjakarta.security.auth.message.config.AuthConfig.isProtected
+ 		Used to determine whether the authentication + context configuration object encapsulates any protected authentication contexts. true
+ 		true
JASPIC:JAVADOC:76voidjakarta.security.auth.message.config.AuthConfig.refresh
+ 		Causes a dynamic anthentication context + configuration object to update the internal state that it uses to process calls to its + getAuthContext method. true
+ 		true
JASPIC:JAVADOC:77AuthConfigFactoryjakarta.security.auth.message.config.AuthConfigFactory.AuthConfigFactory
+
+ 		true
+ 		true
JASPIC:JAVADOC:78String[]jakarta.security.auth.message.config.AuthConfigFactory.detachListener
+ + ( RegistrationListener ,
String ,
String ) + 		Disassociate the listener from all the + provider registrations whose layer and appContext values are matched by the corresponding arguments + to this method. Factories should periodically notify Listeners to effectively detach listeners that + are no longer in use. true
+ 		true
JASPIC:JAVADOC:79AuthConfigProviderjakarta.security.auth.message.config.AuthConfigFactory.getConfigProvider
+ + ( String ,
String ,
RegistrationListener ) + 		Get a registered AuthConfigProvider from the + factory. Get the provider of ServerAuthConfig and ClientAuthConfig objects registered for the + identified message layer and application context. All factories shall employ the following + precedence rules to select the registered AuthConfigProvider that matches the layer and appContext + arguments: The provider specifically registered for the values passed as the layer and appContext + arguments shall be selected. If no provider is selected according to the preceding rule, the + provider specifically registered for the value passed as the appContext argument and for all (that + is, null) layers shall be selected. If no provider is selected according to the preceding rules, the + provider specifically registered for the value passed as the layer argument and for all (that is, + null) appContexts shall be selected. If no provider is selected according to the preceding rules, + the provider registered for all (that is, null) layers and for all (that is, null) appContexts shall + be selected. If no provider is selected according to the preceding rules, the factory shall + terminate its search for a registered provider. The above precedence rules apply equivalently to + registrations created with a null or non-null className argument. true
+ 		true
JASPIC:JAVADOC:80AuthConfigFactoryjakarta.security.auth.message.config.AuthConfigFactory.getFactory
+ 		Get the system-wide AuthConfigFactory + implementation. If a non-null system-wide factory instance is defined at the time of the call, for + example, with setFactory, it will be returned. Otherwise, an attempt will be made to construct an + instance of the default AuthConfigFactory implementation class. The fully qualified class name of + the default factory implementation class is obtained from the value of the + authconfigprovider.factory security property. When an instance of the default factory implementation + class is successfully constructed by this method, this method will set it as the system-wide factory + instance. The absolute pathname of the Java security properties file is + JAVA_HOME/lib/security/java.security, where JAVA_HOME refers to the directory where the JDK was + installed. true
+ 		true
JASPIC:JAVADOC:81RegistrationContextjakarta.security.auth.message.config.AuthConfigFactory.getRegistrationContext
+ + ( String ) + 		Get the the registration context for the + identified registration. true
+ 		true
JASPIC:JAVADOC:82String[]jakarta.security.auth.message.config.AuthConfigFactory.getRegistrationIDs
+ + ( AuthConfigProvider ) + 		Get the registration identifiers for all + registrations of the provider instance at the factory. true
+ 		true
JASPIC:JAVADOC:83voidjakarta.security.auth.message.config.AuthConfigFactory.refresh
+ 		Cause the factory to reprocess its persisent + declarative representation of provider registrations. A factory should only replace an existing + registration when a change of provider implementation class or initialization properties has + occurred. true
+ 		true
JASPIC:JAVADOC:84Stringjakarta.security.auth.message.config.AuthConfigFactory.registerConfigProvider
+ + ( String ,
Map ,
String ,
String ,
String ) + 		Registers within the factory and records + within the factory's persistent declarative representation of provider registrations a provider of + ServerAuthConfig and/or ClientAuthConfig objects for a message layer and application context + identifier. This method typically constructs an instance of the provider before registering it with + the factory. Factories may extend or modify the persisted registrations of existing provider + instances, if those instances were registered with ClassName and properties arguments equivalent to + those passed in the current call. This method employs the two argument constructor required to be + supported by every implementation of the AuthConfigProvider interface, and this method must pass a + null value for the factory argument of the constructor. AuthConfigProviderImpl + AuthConfigProviderImpl(Map properties, AuthConfigFactory factory). At most one registration may + exist within the factory for a given combination of message layer and appContext. Any pre-existing + registration with identical values for layer and appContext is replaced by a subsequent + registration. When replacement occurs, the registration identifier, layer, and appContext identifier + remain unchanged, and the AuthConfigProvider (with initialization properties) and description are + replaced. Within the lifetime of its Java process, a factory must assign unique registration + identifiers to registrations, and must never assign a previously used registration identifier to a + registration whose message layer and or appContext identifier differ from the previous use. + Programmatic registrations performed by using this method must update (according to the replacement + rules described above) the persistent declarative representation of provider registrations employed + by the factory constructor. true
+ 		true
JASPIC:JAVADOC:85Stringjakarta.security.auth.message.config.AuthConfigFactory.registerConfigProvider
+ + ( AuthConfigProvider ,
String ,
String ,
String ) + 		Registers within the (in-memory) factory, a + provider of ServerAuthConfig and/or ClientAuthConfig objects for a message layer and application + context identifier. This method does NOT effect the factory's persistent declarative representation + of provider registrations, and is intended to be used by providers to perform self-Registration. At + most one registration may exist within the factory for a given combination of message layer and + appContext. Any pre-existing registration with identical values for layer and appContext is replaced + by a subsequent registration. When replacement occurs, the registration identifier, layer, and + appContext identifier remain unchanged, and the AuthConfigProvider (with initialization properties) + and description are replaced. Within the lifetime of its Java process, a factory must assign unique + registration identifiers to registrations, and must never assign a previously used registration + identifier to a registration whose message layer and or appContext identifier differ from the + previous use. true
+ 		true
JASPIC:JAVADOC:86booleanjakarta.security.auth.message.config.AuthConfigFactory.removeRegistration
+ + ( String ) + 		Remove the identified provider registration + from the factory (and from the persistent declarative representation of provider registrations, if + appropriate) and invoke any listeners associated with the removed registration. true
+ 		true
JASPIC:JAVADOC:87voidjakarta.security.auth.message.config.AuthConfigFactory.setFactory
+ + ( AuthConfigFactory ) + 		Set the system-wide AuthConfigFactory + implementation. If an implementation was set previously, it will be replaced. Listeners are not + notified of a change to the registered factory. true
+ 		true
JASPIC:JAVADOC:88Stringjakarta.security.auth.message.config.AuthConfigFactory.RegistrationContext.getAppContext
+ 		Get the application context identifier from + the registration context true
+ 		true
JASPIC:JAVADOC:89Stringjakarta.security.auth.message.config.AuthConfigFactory.RegistrationContext.getDescription
+ 		Get the description from the registration + context true
+ 		true
JASPIC:JAVADOC:90Stringjakarta.security.auth.message.config.AuthConfigFactory.RegistrationContext.getMessageLayer
+ 		Get the layer name from the registration + context true
+ 		true
JASPIC:JAVADOC:91booleanjakarta.security.auth.message.config.AuthConfigFactory.RegistrationContext.isPersistent
+ 		Get the persisted status from the + registration context. true
+ 		true
JASPIC:JAVADOC:92ClientAuthConfigjakarta.security.auth.message.config.AuthConfigProvider.getClientAuthConfig
+ + ( String ,
String ,
CallbackHandler ) + 		Get an instance of ClientAuthConfig from this + provider. The implementation of this method returns a ClientAuthConfig instance that describes the + configuration of ClientAuthModules at a given message layer, and for use in an identified + application context. true
+ 		true
JASPIC:JAVADOC:93ClientAuthConfigjakarta.security.auth.message.config.AuthConfigProvider.getClientAuthConfig
+ + ( String ,
String ,
CallbackHandler )
throws AuthException
+ 		If this provider does not support the + assignment of a default CallbackHandler to the returned ClientAuthConfig.true
+ 		true
JASPIC:JAVADOC:94ServerAuthConfigjakarta.security.auth.message.config.AuthConfigProvider.getServerAuthConfig
+ + ( String ,
String ,
CallbackHandler ) + 		Get an instance of ServerAuthConfig from this + provider. The implementation of this method returns a ServerAuthConfig instance that describes the + configuration of ServerAuthModules at a given message layer, and for a particular application + context. true
+ 		true
JASPIC:JAVADOC:95ServerAuthConfigjakarta.security.auth.message.config.AuthConfigProvider.getServerAuthConfig
+ + ( String ,
String ,
CallbackHandler )
throws AuthException
+ 		If this provider does not support the + assignment of a default CallbackHandler to the returned ServerAuthConfig.true
+ 		true
JASPIC:JAVADOC:96voidjakarta.security.auth.message.config.AuthConfigProvider.refresh
+ 		Causes a dynamic configuration provider to + update its internal state such that any resulting change to its state is reflected in the + corresponding authentication context configuration objects previously created by the provider within + the current process context. true
+ 		true
JASPIC:JAVADOC:97ClientAuthContextjakarta.security.auth.message.config.ClientAuthConfig.getAuthContext
+ + ( String ,
Subject ,
Map ) + 		Get a ClientAuthContext instance from this + ClientAuthConfig. The implementation of this method returns a ClientAuthContext instance that + encapsulates the ClientAuthModules used to secure and validate requests/responses associated with + the given authContextID. Specifically, this method accesses this ClientAuthConfig object with the + argument authContextID to determine the ClientAuthModules that are to be encapsulated in the + returned ClientAuthContext instance. The ClientAuthConfig object establishes the request and + response MessagePolicy objects that are passed to the encapsulated modules when they are initialized + by the returned ClientAuthContext instance. It is the modules' responsibility to enforce these + policies when invoked. true
+ 		true
JASPIC:JAVADOC:98ClientAuthContextjakarta.security.auth.message.config.ClientAuthConfig.getAuthContext
+ + ( String ,
Subject ,
Map )
throws AuthException
+ 		If this method fails.true
+ 		true
JASPIC:JAVADOC:99voidjakarta.security.auth.message.config.RegistrationListener.notify
+ + ( String ,
String ) + 		Notify the listener that a registration with + which it was associated was replaced or unregistered. When a RegistrationListener is associated with + a provider registration within the factory, the factory must call its notify method when the + corresponding registration is unregistered or replaced. true
+ 		true
JASPIC:JAVADOC:100ServerAuthContextjakarta.security.auth.message.config.ServerAuthConfig.getAuthContext
+ + ( String ,
Subject ,
Map ) + 		Get a ServerAuthContext instance from this + ServerAuthConfig. The implementation of this method returns a ServerAuthContext instance that + encapsulates the ServerAuthModules used to validate requests and secure responses associated with + the given authContextID. Specifically, this method accesses this ServerAuthConfig object with the + argument authContextID to determine the ServerAuthModules that are to be encapsulated in the + returned ServerAuthContext instance. The ServerAuthConfig object establishes the request and + response MessagePolicy objects that are passed to the encapsulated modules when they are initialized + by the returned ServerAuthContext instance. It is the modules' responsibility to enforce these + policies when invoked. true
+ 		true
JASPIC:JAVADOC:101ServerAuthContextjakarta.security.auth.message.config.ServerAuthConfig.getAuthContext
+ + ( String ,
Subject ,
Map )
throws AuthException
+ 		If this method fails.true
+ 		true
JASPIC:JAVADOC:102Class[]jakarta.security.auth.message.module.ClientAuthModule.getSupportedMessageTypes
+ 		Get the one or more Class objects + representing the message types supported by the module. true
+ 		true
JASPIC:JAVADOC:103voidjakarta.security.auth.message.module.ClientAuthModule.initialize
+ + ( MessagePolicy ,
MessagePolicy ,
CallbackHandler ,
Map ) + 		Initialize this module with request and + response message policies to enforce, a CallbackHandler, and any module-specific configuration + properties. The request policy and the response policy must not both be null. true
+ 		true
JASPIC:JAVADOC:104voidjakarta.security.auth.message.module.ClientAuthModule.initialize
+ + ( MessagePolicy ,
MessagePolicy ,
CallbackHandler ,
Map )
throws + AuthException
+ 		If module initialization fails, including for + the case where the options argument contains elements that are not supported by the module.true
+ 		true
JASPIC:JAVADOC:105Class[]jakarta.security.auth.message.module.ServerAuthModule.getSupportedMessageTypes
+ 		Get the one or more Class objects + representing the message types supported by the module. true
+ 		true
JASPIC:JAVADOC:106voidjakarta.security.auth.message.module.ServerAuthModule.initialize
+ + ( MessagePolicy ,
MessagePolicy ,
CallbackHandler ,
Map ) + 		Initialize this module with request and + response message policies to enforce, a CallbackHandler, and any module-specific configuration + properties. The request policy and the response policy must not both be null. true
+ 		true
JASPIC:JAVADOC:107voidjakarta.security.auth.message.module.ServerAuthModule.initialize
+ + ( MessagePolicy ,
MessagePolicy ,
CallbackHandler ,
Map )
throws + AuthException
+ 		If module initialization fails, including for + the case where the options argument contains elements that are not supported by the module.true
+ 		true
+ + diff --git a/tck/spi/SpecAssertions.html b/tck/spi/SpecAssertions.html new file mode 100644 index 0000000..78a06de --- /dev/null +++ b/tck/spi/SpecAssertions.html @@ -0,0 +1,4203 @@ + + + + + +Specification Assertion Detail + + +
+
+

+ Jakarta Authentication - 3.1.0
Specification Assertion Detail +

+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
TotalsTotalActiveDeprecatedRemoved
# of Assertions 25324670
# of Required Assertions 23122470
# of Optional Assertions 222200
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
IDChapterSectionDescriptionRequiredDependencyImplementation SpecificDefined byStatusTestable
JASPIC:SPEC:111.1 A message processing runtime may acquire the + authentication context objects that it uses to invoke authentication modules by interacting with an + authentication context configuration object true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:211.1 An authentication context configuration + object is an implementation of either the ClientAuthConfig or ServerAuthConfig interface as defined + by this specification. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:311.3 A message processing runtime may acquire + authentication context configuration objects by interacting with a provider of authentication + context configuration objects. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:411.4 A message processing runtime may interact + with the factory to obtain or establish the provider registered for an application context and + messaging layer. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:511.7 Authentication modules should be implemented + such that they may be invoked concurrently and such that they are able to apply and establish + independent security identities for concurrent invocations. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:611.7 In a multi-message authentication scenario, + it is the responsibility of the authentication modules involved in the authentication to tie + together or correlate the messages that comprise the authentication exchange. In addition to message + correlation to tie to together the messages required to complete an authentication, message + correlation may also be employed post-authentication such that a prior authentication result or + session may be applied to a subsequent invocation. Modules are expected to perform their message + correlation function based on the parameters of their invocation and with the benefit of any + additional facilities provided by the invoking runtime (e.g., via their CallbackHandler). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:721.1 A message processing runtime that wishes to + invoke authentication modules configured according to this specification, must use the + AuthConfigFactory.getFactory method to obtain a factory implementation. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:821.1 The runtime must invoke the getConfigProvider + method of the factory to obtain the AuthConfigProvider. The runtime must specify appropriate + (non-null) layer and application context identifiers in its call to getConfigProvider. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:921.1 A runtime may continue to reuse a provider + for as long as it wishes. However, a runtime that wishes to be notified of changes to the factory + that would cause the factory to return a different provider for the layer and appContext arguments + should include a (non-null) RegistrationListener as an argument in the call used to acquire the + provider. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:1021.1.2 The factory implementation must satisfy the + requirements defined by the AuthConfigFactory class. In particular, it must offer a public, zero + argument constructor that supports the construction and registration of AuthConfigProvider objects + from a persistent declarative representation. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1121.2 Once the runtime has obtained the appropriate + (non-null) AuthConfigProvider, it must obtain from the provider the authentication context + configuration object corresponding to the messaging layer, its role as client or server, and the + application context for which it will be exchanging messages. It does this by invoking + getClientAuthConfig or getServerAuthConfig as appropriate to the role of the runtime in the message + exchange. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1221.2 A runtime operating at points 1 and 4 in the + messaging model must invoke getClientAuthConfig to acquire its configuration object. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1321.2 A runtime operating at points 2 and 3 in the + messaging model must invoke getServerAuthConfig to acquire its configuration object. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1421.2 The call to acquire the configuration object + must specify the same values for layer and application context identifier that were used to acquire + the provider true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1521.2 A runtime may continue to reuse an acquired + authentication context configuration object for as long as it is acting as client or server of the + corresponding application. A runtime should reacquire an authentication context configuration object + when it is notified (via a RegistrationListener) that it must reacquire the AuthConfigProvider from + which the configuration object was acquired (and after having reacquired the provider). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:1621.2.2 The provider implementation must satisfy the + requirements defined by the AuthConfigProvider interface. In particular, it must return non-null + authentication configuration objects. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:1721.2.2 When the provider is a dynamic configuration + provider, any change to the internal state of the provider occurring as the result of a call to its + refresh method must be recognized by every authentication context configuration object obtained from + the provider. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:1821.2.2 The provider implementation must provide a + configuration facility that may be used to configure the information required to initialize + authentication contexts for the (one or more) authentication context configuration scopes (defined + by layer and application context) for which the provider is registered (at the factory). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:1921.3 At points (1) and (2) in the messaging model, + the message processing runtime must obtain the authentication context identifier corresponding to + the request message processing being performed by the runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:2021.3 The identifier may be acquired by calling the + getOperation method of the authentication context configuration object (obtained in the preceding + step). If the messaging runtime chooses to obtain the operation identifier by this means, it must + provide a MessageInfo object as argument to the getOperation call, and the MessageInfo must have + been initialized such that its getRequestMessage method will return the request message being + processed by the runtime. The type of the returned request message must be as defined by the profile + of this specification being followed by the messaging runtime. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2121.3 Alternatively and depending on the + requirements relating to operation identifier inherent in the profile being followed by the + messaging runtime, the runtime may obtain the operation identifier by other means. Where a profile + defines or facilitates other means by which a messaging runtime may acquire the operation + identifier, the identifier acquired by any such means must be equivalent to the identifier that + would be acquired by calling getOperation as described above. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2221.3.2 The configuration implementation must satisfy + the requirements defined by the AuthConfig interface with respect to the getOperation method. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2321.4 At points (1) and (2) in the messaging model, + the message processing runtime must invoke the getAuthContext method of the authentication context + configuration object (obtained in step 2) to obtain the authentication context object corresponding + to the message that is to be processed. This is accomplished by invoking getAuthContext with the + operation/message identifier corresponding to the request message and obtained as described above. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:2421.4 If required by the profile of this + specification being followed by the runtime, the call to getAuthContext must pass a Map containing + the required property elements. The value of the Subject argument provided by the runtime in its + call to getAuthContext must correpond to the requirements of the profile of this specification being + followed by the runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:2521.4 Once an authentication context is acquired, + it may be reused to process subsequent requests of the application for which an equivalent + authentication context identifier, Subject, and properties Map (as used in the getAuthContext) + applies. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2621.4 Runtimes that wish to be dynamic with respect + to changes in context configuration, should call getAuthContext for every request. An authentication + context configuration object may return the same authentication context object for different + authentication context identifiers for which the same module configuration and message protection + policy applies. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2721.4 At points (3) and (4) in the messaging model, + the runtime may repeat the context acquisition performed at point (2) and (1) respectively, or it + may reuse the previously acquired context. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2821.4 The configuration implementation must satisfy + the requirements defined by the corresponding ClientAuthConfig or ServerAuthConfig interface with + respect to the getAuthContext method. In this regard, the configuration implementation must + determine the authentication modules that are to comprise the acquired context, and it must provide + the context implementation with sufficient information to initialize the modules of the context. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:2921.4 The getAuthContext method must return null + when no authentication modules are to be invoked for an identified authentication context at the + layer and application context represented by the configuration object true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:3021.4 The AuthConfigProvider from which the + authentication context configuration object was acquired must provide a configuration facility by + which the information required to initialize authentication contexts may be configured and + associated with one or more authentication context identifiers within the (one or more) layer and + application context scopes for which the provider is registered (at the factory). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3121.5 Every context implementation must satisfy the + requirements as defined by the corresponding ClientAuthContext or ServerAuthContext interface. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3221.5 Every context must delegate calls made to the + methods of its corresponding ClientAuth or ServerAuth interface to the corresponding methods of its + one or more authentication modules. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3321.5 When a context encapsulates multiple + authentication modules, the context must embody the control logic to determine which modules of the + context are to be invoked and in what order. Contexts which encapsulate alternative sufficient + modules, must ensure that the same message values are passed to each invoked alternative of the + context. When a context invokes multiple authentication modules, the context must combine the + AuthStatus values returned by the invoked authentication modules to establish the AuthStatus value + returned by the context to the messaging runtime. The context implementation must define the logic + for combining the returned AuthStatus values. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3421.5 If a non-null authentication context object + is returned by getAuthContext, the corresponding message processing runtime must invoke the methods + of the acquired authentication context to process the corresponding request and response messages as + defined below. Otherwise, the message processing runtime, must proceed with its normal processing of + the corresponding messages and without invoking the methods of an authentication context object. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3521.5 At point (1) in the message processing model + : the message processing runtime must call the secureRequest method of the ClientAuthContext. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:3621.5 (At point 1 in message processing model) The + messageInfo argument to the call must have been initialized such that its getRequestMessage method + will return the request message being processed by the runtime. The type of the returned request + message must be as defined by the profile being followed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:3721.5 (At point 1 in message processing model) If a + non-null Subject was used to acquire the ClientAuthContext, the same Subject must be passed as the + clientSubject in this call. If a non-null clientSubject is used in this call, it must not be + read-only, and the same clientSubject argument must be passed in all calls to validateResponse made + for the one or more responses processed to complete the message exchange. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:3821.5 (At point 1 in message processing model) If + the call to secureRequest returns: AuthStatus.SEND_SUCCESS - the runtime should send (without + calling secureRequest) the request message acquired by calling messageInfo.getRequestMessage. After + sending the request, the runtime should proceed to point (4) in the message processing model (to + receive and validate the response). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:3921.5 (At point 1 in message processing model) If + the call to secureRequest returns: AuthStatus.SEND_CONTINUE - the module has returned, in + messageInfo, an initial request message to be sent. Moreover, the module is informing the client + runtime that it will be required to continue the message dialog by sending the message resulting + from validation of the response to the initial message. If the runtime will be unable to continue + the dialog by sending the message resulting from validation of the response, the runtime must not + send the initial request and it must convey its inability by returning an error to the client + application. Otherwise, the runtime should send (without calling secureRequest) the request message + acquired by calling messageInfo.getRequestMessage. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4021.5 (At point 1 in message processing model) If + the call to validateRequest returns: AuthStatus.FAILURE (Befor service Invocation) - The runtime + should return an error to the client application. The runtime should derive the returned error from + the response message acquired by calling messageInfo.getResponseMessage. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4121.5 (At point 1 in message processing model) If + the call to secureRequest throws an AuthException - the runtime should use the exception to convey + to the client runtime that the request failed. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4221.5 At point (4) in the message processing model: + the message processing runtime must call the validateResponse method of the ClientAuthContext. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4321.5 In the call made to validateResponse, the + runtime must pass the same MessageInfo instance that was passed to secureRequest (at the start of + the message exchange). The messageInfo argument must have been initialized such that its + getResponseMessage method will return the response message being processed by the runtime.The type + of the required return messages must be as defined by the profile being followed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:4421.5 The value of the clientSubject argument to + the (validateResponse) call must be the same as that passed in the call to secureRequest for the + corresponding request. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:4521.5 The serviceSubject argument to the + (validateResponse) call may be non-null, in which it may be used by modules to store Principals and + credentials determined to pertain to the source of the response. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4621.5 If the call to validateResponse returns: + AuthStatus.SUCCESS - The runtime should use the response message acquired by calling + messageInfo.getResponseMessage.to create the return value to be returned to the client. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4721.5 If the call to validateResponse returns: + AuthStatus.SEND_CONTINUE - if the runtime it is unable to process this status value it must return + an error to the client application indicating its inability to process this status value. To process + this status value, the runtime must send (without calling secureRequest) the (continuation) request + message obtained by calling messageInfo.getRequestMessage, and it must receive and process via + validateResponse (at least) the next corresponding response or error (before returning a value to + the client). true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:4821.5 If the call to validateResponse returns: + AuthStatus.FAILURE- the runtime should return an error to the client application. The runtime should + derive the returned error from the response message acquired by calling + messageInfo.getResponseMessage. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:4921.5 If the call to validateResponse throws an + AuthException - runtime should use the exception to convey to the client runtime that the request + failed. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:5021.5 At point (2) in the message processing model: + the message processing runtime must call the validateRequest method of the ServerAuthContext. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5121.5 (at point 2 in MPR model) The messageInfo + argument to the call must have been initialized such that its getRequestMessage method will return + the request message being processed by the runtime. For some profiles of this specification, the + runtime must also initialize messageInfo such that its getResponseMessage method will return the + response message being processed by the runtime. The type of the required return messages must be as + defined by the profile being followed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5221.5 (At point (2) in the message processing + model) The clientSubject argument must be non-null and it must not be read-only. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5321.5 (At point (2) in the message processing + model) If a non-null Subject was used to acquire the ServerAuthContext, the same Subject must be + passed as the serviceSubject in this call. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:31321.5.2 (At point (2) in the message processing + model) If a non-null serviceSubject is used in this call, it must not be read-only. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:31421.5.2 (At point (2) in the message processing + model) the same serviceSubject must be passed in the call to secureResponse for the corresponding + response (if there is one). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:5421.5 If the call to validateRequest returns: + AuthStatus.SUCCESS - the runtime should proceed to authorize the request using the clientSubject, + perform the application request processing (depending on the authorization result), and proceed to + point (3) as appropriate. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:5521.5 If the call to validateRequest returns: + AuthStatus.SEND_SUCCESS - The runtime must NOT proceed to authorize the request or perform the + application request processing. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5621.5 If the call to validateRequest returns: + AuthStatus.SEND_CONTINUE - The runtime must NOT proceed to authorize the request or perform the + application request processing. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5721.5 If the call to validateRequest returns: + AuthStatus.SEND_FAILURE - (If the failure occurred after the service invocation), the runtime must + perform whatever processing it requires to complete the processing of a request that failed after a + successful service invocation, and prior to communicating the invocation result to the client + runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:31521.5 If the call to validateRequest returns: + AuthStatus.SEND_FAILURE - (If the failure occurred befor the service invocation), the runtime must + NOT proceed to authorize the request or perform the application request processing. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:5821.5 If the call to validateRequest throws an + AuthException (Befor Service Invocation) - the runtime must NOT proceed to authorize the request or + perform the application request processing. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:31621.5 If the call to validateRequest throws an + AuthException - (If the failure occurred after the service invocation) the runtime must perform + whatever processing it requires to complete the processing of a request that failed after a + successful service invocation, and prior to communicating the invocation result to the client + runtime. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:5921.5 At point (3) in the message processing model: + the message processing runtime must call the secureResponse method of the ServerAuthContext. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:6021.5 In the call made to secureResponse, the + runtime must pass the same MessageInfo instance that was passed to validateRequest (for the + corresponding request message). The messageInfo argument must have been initialized such that its + getResponseMessage method will return the response message being processed by the runtime. The type + of the required return messages must be as defined by the profile being followed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:6121.5 The value of the serviceSubject argument to + the (secureResponse) call must be the same as that passed in the call to validateRequest for the + corresponding request. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:6221.5 If the call to secureResponse returns: + AuthStatus.SEND_SUCCESS - the runtime should send (without calling secureResponse) the response + message acquired by calling messageInfo.getResponseMessage at which time, the processing of the + application request and its corresponding response will be complete. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:6321.5 If the call to secureResponse returns: + AuthStatus.SEND_CONTINUE - the runtime should send (without calling secureResponse) the response + message acquired by calling messageInfo.getResponseMessage. The processing of the response is not + finished, and as such, its outcome is not yet known. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:6421.5 If the call to secureResponse returns: + AuthStatus.SEND_FAILURE - the runtime must perform whatever processing it requires to complete the + processing of a request that failed after (or during) service invocation, and prior to communicating + the invocation result to the client runtime. This may include sending (without calling + secureResponse) the response message acquired by calling messageInfo.getResponseMessage. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:6521.5 If the call to secureResponse throws an + AuthException - the runtime must perform whatever processing it requires to complete the processing + of a request that failed after (or during) service invocation, and prior to communicating the + invocation result to the client runtime. the runtime may send (without calling secureResponse) an + appropriate response message of its choice. if a failure message is returned, it should indicate + that the failure in request processing occurred after the successful invocation of the service. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:6621.5 The authentication module implementations + within the context must satisfy the requirements as defined by the corresponding ClientAuthModule or + ServerAuthModule interface. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:6731 The message layer value used to select the + AuthConfigProvider and ServerAuthConfig objects for this (servlet) profile must be HttpServlet true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:6832 The application context identifier (that is, + the appContext parameter value) used to select the AuthConfigProvider and ServerAuthConfig objects + for a specific application shall be the String value constructed by concatenating the host name, a + blank separator character, and the decoded context path corresponding to the web module. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:6933 The MessageInfo argument used in any call + made by the message processing runtime to validateRequest or secureResponse must have been + initialized such that the non-null objects returned by the getRequestMessage and getResponseMessage + methods of the MessageInfo are an instanceof HttpServletRequest and HttpServletResponse, + respectively. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7034 The getSupportedMessageTypes method of all + authentication modules integrated for use with this profile, must include + jakarta.servlet.http.HttpServletRequest.class and jakarta.servlet.http.HttpServeletResponse.class in + its return value. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:7135 The CallbackHandler passed to + ServerAuthModule.initialize is determined by the handler argument passed in the + AuthConfigProvider.getServerAuthConfig call that acquired the corresponding authentication context + configuration object. The handler argument must not be null. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:7235 The CallbackHandler passed to + ServerAuthModule.initialize must support the following callbacks: CallerPrincipalCallback, + GroupPrincipalCallback, PasswordValidationCallback. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7335 The argument handler and the CallbackHandler + passed through to the authentication modules must be initialized with any application context + required to process its supported callbacks on behalf of the corresponding application. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:31836 The factory implementation returned by + calling the getFactory method of the abstract AuthConfigFactory class must have been configured such + that it returns a non-null AuthConfigProvider for those application contexts for which pluggable + authentication modules have been configured at the ?HttpServlet? layer. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:7436 For each application context for which it is + servicing requests, the runtime must call getConfigProvider to acquire the provider object + corresponding to the layer and application context. The layer and appContext arguments to + getConfigProvider must be as defined in Section 3.1, Message Layer Identifier and Section 3.2, + Application Context Identifier respectively true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7536 If a non-null AuthConfigProvider is returned, + the messaging runtime must call getServerAuthConfig on the provider to obtain the authentication + context configuration object pertaining to the application context at the layer. The layer and + appContext arguments of the call to getServerAuthConfig must be the same as those used to acquire + the provider, and the handler argument must be as defined in Section 3.5, CallbackHandler + Requirements. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7636 A null return value from getConfigProvider + indicates that pluggable authentication modules have not been configured at the layer for the + application context and that the messaging runtime must proceed to perform its servlet security + constraint processing without reliance on this profile. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:7737 When a non-null AuthConfigProvider is + returned by the factory, the provider must have been configured with the information required to + initialize the authentication contexts for the (one or more) authentication context configuration + scopes (defined by layer and application context) for which the provider is registered (at the + factory). true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7837 When a non-null AuthConfigProvider is + returned by the factory, the messaging runtime must call getAuthContext on the authentication + context configuration object (obtained from the provider). true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:7937 For all values of the authContextID argument + that satisfy the requirements of Section 3.7.1, the call to getAuthContext must return a non-null + authentication context. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:8037.1 the authentication context identifier used in + the call to getAuthContext must be equivalent to the value that would be acquired by calling + getAuthContextID with the MessageInfo that will be used in the call to validateRequest. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:8137.2 A null value may be passed as the Subject + argument in the getAuthContext call. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:30037.2 If the runtime is a Jakarta Authorization compatible + Servlet container, the properties argument passed in all calls to getAuthContext must contain the + following key-value pair: (key) jakarta.security.jacc.PolicyContext (value) The PolicyContext + identifier value that the container must set. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:8337.3 When the runtime is not a Jakarta Authorization compatible + Servlet container, the properties argument used in all calls to getAuthContext must not include a + jakarta.security.jacc.PolicyContext key-value pair, and a null value may be passed for the + properties argument. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:8437.4 Each ServerAuthContext obtained via + getAuthContext must initialize its encapsulated ServerAuthModule objects with a non-null value for + requestPolicy. The encapsulated authentication modules may be initialized with a null value for + responsePolicy. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:8537.4 The requestPolicy used to initialize the + authentication modules of the ServerAuthContext must be constructed such that the value obtained by + calling isMandatory on the requestPolicy accurately reflects whether (i.e., true return value) or + not (i.e, false return value) authentication is required to access the web resource corresponding to + the HttpServletRequest to which the ServerAuthContext will be applied. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:8637.4 The message processing runtime is responsible + for determining if authentication is required and must convey the results of its determination as + described in Section 3.8.1, 'MessageInfo Requirements,' on page 29. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:8737.4 Calling getTargetPolicies on the request + MessagePolicy must return an array containing at least one TargetPolicy whose ProtectionPolicy will + be interpreted by the modules of the context to mean that the source of the corresponding targets + within the message is to be authenticated. To that end, calling the getID method on the + ProtectionPolicy must return one of the following values: ProtectionPolicy.AUTHENTICATE_SENDER, + ProtectionPolicy.AUTHENTICATE_CONTENT true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:8838 At point (2) in the message processing model, + the runtime must call validateRequest on the ServerAuthContext. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:8938 If the request has satisfied the connection + requirements, the message processing runtime must call validateRequest independent of whether or not + access to the resource would be authorized prior to the call to validateRequest. validateRequest + must be called for all requests, including requests to a form-based login form. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9038 If the call to validateRequest returns + AuthStatus.SUCCESS, the runtime must establish return values for getUserPrincipal, getRemoteUser, + and getAuthType as defined in Section 3.8.4. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30138 If the applicable requestPolicy indicates + that authentication is NOT required, the runtime may choose to continue the invocation of the + resource under the runtime?s representation of the unauthenticated caller identity. A runtime must + not choose to continue the invocation if the HttpServletResponse.isCommitted() returns true. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:9138 In a Jakarta Authorization compatible runtime, the identity + must be comprised of exactly the Principal objects of the clientSubject. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:9238 In a non-Jakarta Authorization compatible Servlet runtime, + the identity must include the caller Principal (established during the validateRequest processing + using the corresponding CallerPrincipalCallback). (and may include any of the Principal objects of + the clientSubject.) true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9338 If the request is not authorized, the runtime + must return the HTTP status code required by the Servlet spec. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:31738 The request must be dispatched to the + resource if the request was determined to be authorized; otherwise it must NOT be dispatched and the + runtime must proceed to point (3) in the message processing model. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30238 If the request is dispatched to the resource + and the resource invocation throws an exception to the runtime, the runtime must set, within the + response, an HTTP status code which satisfies any applicable requirements defined within the servlet + specification. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:30338 If the request is dispatched to the resource, + and the resource was configured to run-as its caller, then for invocations originating from the + resource where caller propagation is required, the identity established using the + CallerPrincipalCallback must be used as the propagated identity true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9438 The call to secureResponse must not be made + if the resource throws an exception to the calling runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30438 If invocation of the resource completes + without throwing an exception, the runtime must proceed to point (3) in the message processing + model. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30538 At point (3) in the message processing model, + the runtime must call secureResponse on the same ServerAuthContext used in the corresponding call to + validateRequest and with the same MessageInfo object. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9538.1 The messageInfo argument used in the call to + validateRequest must have been initialized by the runtime such that its getRequestMessage and + getResponseMessage methods will return the HttpServletRequest and HttpServletResponse objects + corresponding to the messages (respectively) being processed by the runtime. This must be the case + even when the target of the request is a static page (that is, not a servlet). true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30638.1.1 This profile requires that the message + processing runtime conditionally establish the following key-value pair within the Map of the + MessageInfo object passed in the calls to getAuthContextID, validateRequest, and secureResponse. + (key) jakarta.security.auth.message.MessagePolicy.isMandatory (val) Any non-null String value, s, + for which Boolean.valueOf(s).booleanValue() == true. The MessageInfo map must contain this key and + its associated value, if and only if authentication is required to perform the resource access + corresponding to the HttpServletRequest to which the ServerAuthContext will be applied. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:30738.1.1 Authentication is required if use of the HTTP + method of the HttpServletRequest at the resource identified by the HttpServletRequest is covered by + a Servlet auth-constraint, or in a Jakarta Authorization compatible runtime, if the corresponding + WebResourcePermission is NOT granted2 to an unauthenticated caller true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:31938.1.1 In a Jakarta Authorization compatible runtime, the + corresponding WebResourcePermission may be constructed directly from the HttpServletRequest as + follows: public WebResourcePermission(HttpServletRequest request); The authentication context + configuration system must use the value of this property to establish the corresponding value within + the requestPolicy passed to the authentication modules of the ServerAuthContext acquired to process + the MessageInfo.t true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:9638.2 A new clientSubject must be instantiated and + passed in the call to validateRequest. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9738.3 validateRequest may be called either before + the service invocation (to establish the caller identity) or after the service invocation (when a + multi-message dialog is required to secure the response). The module implementation is responsible + for recording any state and performing any processing required to differentiate these two different + types of calls to validateRequest. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:9838.3.1 When validateRequest is called before the + service invocation on a module initialized with a mandatory requestPolicy (as defined by the return + value from requestPolicy.isMandatory()), the module must only return AuthStatus.SUCCESS if it was + able to completely satisfy the request authentication policy. In this case, the module (or its + context) must also have used the CallbackHandler passed to it by the runtime to handle a + CallerPrincipalCallback using the clientSubject as argument to the callback. If more than one module + of a context uses the CallbackHandler to handle this callback, the context is responsible for + coordinating the calls such that the appropriate caller principal value is established. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:9938.3.1 If the module was not able to completely + satisfy the request authentication policy, it must: return AuthStatus.SEND_CONTINUE - if it has + established a response (available to the runtime by calling messageInfo.getResponseMessage) that + must be sent by the runtime for the request validation to be effectively continued by the client. + The module must have set the HTTP status code of the response to a value (e.g., HTTP 401 + unauthorized, HTTP 303 see other, or HTTP 307 temporary redirect) that will indicate to the client + that it should retry the request. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10038.3.1 If the module was not able to completely + satisfy the request authentication policy, it must: return AuthStatus.SEND_FAILURE - if the request + validation failed, and when the client should not retry the request. The module must have + established a response message (available to the runtime by calling messageInfo.getResponseMessage) + that may be sent by the runtime to inform the client that the request failed. The module must have + set the HTTP status code of the response to a value (e.g., HTTP 403 forbidden or HTTP 404 not found) + that will indicate to the client that it should NOT retry the request. The runtime may choose not to + send a response message, or to send a different response message (given that it also contains an + analogous HTTP status code). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10138.3.1 If the module was not able to completely + satisfy the request authentication policy, it must: throw an AuthException - if the request + validation failed, and when the client should not retry the request, and when the module has not + defined a response, to be sent by the runtime. If the runtime chooses to send a response, it must + define the HTTP status code and descriptive content (of the response). The HTTP status code of the + response must indicate to the client (e.g., HTTP 403 forbidden, HTTP 404 not found, or HTTP 500 + internal server error) that the request failed and that it should NOT be retried. The decriptive + content set in the response may be obtained from the AuthException. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10238.3.1 When validateRequest is called before the + service invocation on a module that was initialized with an optional requestPolicy (i.e., + requestPolicy.isMandatory() returns false), the module should attempt to satisfy the request + authentication policy, but it must do so without requiring additional messages or interactions + involving the client. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10338.3.1 If the module returns AuthStatus.SUCCESS (and + the authentication policy was satisfied), the module (or its context) must employ a + CallerPrincipalCallback. If the authentication policy was not satisfied, and yet the module chooses + to return AuthStatus.SUCCESS, the module (or its context) must use a CallerPrincipalCallback to + establish the containers representation of the unauthenticated caller within the clientSubject. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:32038.3.1 If the module throws an AuthException, or + returns any value other that AuthStatus.SUCCESS, the runtime must NOT proceed to the service + invocation. The runtime must process an AuthException as described above for a request with a + mandatory requestPolicy. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:10438.3.2 When validateRequest is called after the + service invocation, the module must return AuthStatus.SEND_SUCCESS when the module has successfully + secured the application response message and made it available through + messageInfo.getResponseMessage. The module must have set the HTTP status code within the response to + HTTP 200 (OK). For the request to be successfully completed, the runtime must send the response + message returned by the module. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10538.3.2 If the module returns + AuthStatus.SEND_FAILURE, it must have established a response message in messageInfo, and it must + have set the HTTP status code within the response to HTTP 500 (internal server error). The runtime + may choose not to send a response message, or to send a different response message (given that it + also contains an HTTP 500 status code). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10638.3.2 When the module throws an AuthException, the + runtime may chose not to send a response. If the runtime sends a response, the runtime must set the + HTTP status code to HTTP 500 (internal server error), and the runtime must define the decriptive + content of the response (perhaps by obtaining it from the AuthException). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10738.3.2 The module must return + AuthStatus.SEND_CONTINUE if the response dialog is to continue. This status value is used to inform + the calling runtime that, to successfully complete the response processing, it will need to be + capable of continuing the message dialog by processing at least one additional request/response + exchange (after having sent the response message returned in messageInfo). The module must have + established (in messageInfo) a response message that will cause the client to continue the response + processing (i.e., retry the request). For the response processing to be successfully completed, the + runtime must send the response message returned by the module. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:10838.3.3 When secureResponse is called on a module + that was initialized with an undefined responsePolicy (i.e., responsePolicy == null), the module + must return AuthStatus.SUCCESS. Otherwise, the AuthStatus return value and AuthException semantics + of secureResponse are as defined in Section 3.8.3.2, validateRequest After Service Invocation. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:30838.3.4 A ServerAuthModule must only call + MessageInfo.setResponseMessage() to wrap or unwrap the existing response within MessageInfo. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:30938.3.4 During secureResponse processing, a + ServerAuthModule must unwrap the messages in MessageInfo that it wrapped during its validateRequest + processing. The unwrapped values must be established in MessageInfo when secureResponse returns. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:31038.3.4 During validateRequest processing, a + ServerAuthModule must NOT unwrap a message in MessageInfo, and must NOT establish a wrapped message + in MessageInfo unless the ServerAuthModule returns AuthStatus.SUCCESS. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:31138.3.4 When a ServerAuthModule returns a wrapped + message in MessageInfo, or unwraps a message in MessageInfo, the message processing runtime must + ensure that the HttpServletRequest and HttpServletResponse objects established by the + ServerAuthModule are used in downstream processing. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:32138.4 The message processing runtime must fulfill + the requirements defined in this section when, at point (2) in the messaging model, validateRequest + returns AuthStatus.SUCCESS. In this case, the runtime must modify the HttpServletRequest as + necessary to ensure that the Principal returned by getUserPrincipal and the String returned by + getRemoteUser correspond, respectively, to the Principal established by validateRequest (via the + CallerPrincipalCallback) and to the String obtained by calling getName on the established Principal. + (Except when getUserPrincipal returns null; in which case the value returned by getRemoteUser must + be null) true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:32238.4 The runtime must also ensure that the value + returned by calling getAuthType on the HttpServletRequest is consistent in terms of being null or + non-null with the value returned by getUserPrincipal. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:32338.4 When getAuthType is to return a non-null + value, the runtime must consult the Map of the MessageInfo object used in the call to + validateRequest to determine if it contains an entry for the key identified in the following table. + If the Map contains an entry for the key, the runtime must obtain (from the Map) the value + corresponding to the key and establish it as the getAuthType return value. (from Table 2-2, the + key=jakarta.servlet.http.authType and the value=a non-null String value) true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:32438.4 (When getAuthType is to return a non-null + value, the runtime must consult the Map of the MessageInfo object used in the call to + validateRequest to determine if it contains an entry for the key identified in the following table.) + If the Map does not contain an entry for the key, and an auth-method is defined in the login-config + element of the deployment descriptor for the web application, the runtime must establish the value + from the auth-method as the value returned by getAuthType. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:32538.4 (When getAuthType is to return a non-null + value, the runtime must consult the Map of the MessageInfo object used in the call to + validateRequest to determine if it contains an entry for the key identified in the following table.) + If the Map does not contain an entry for the key, and the deployment descriptor does not define an + auth-method, the runtime must establish a non-null value of its choice as the value returned by + getAuthType. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:10940 This profile is composed of two internal + profiles that partition the requirements of the profile into those that must be satisfied by client + runtimes and those that must be satisfied by server runtimes. This profile is equally applicable to + SOAP versions 1.1 and 1.2. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:11041 The message layer value used to select the + AuthConfigProvider and ServerAuthConfig objects for this profile must be SOAP true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11142 The application context identifier (i.e., the + appContext parameter value) used by a client runtime to select the AuthConfigProvider, + ClientAuthConfig objects pertaining to a client-side application context configuration scope must be + as defined in Section 4.8.1. Similarly the application context identifier used by a server runtime + to select the AuthConfigProvider and ClientAuthConfig objects pertaining to an server-side + application context configuration scope must be defined in Section 4.9.1 true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11243 The MessageInfo argument used in any call + made by the message processing runtime to secureRequest, validateResponse, validateRequest, or + secureResponse must have been initialized such that the non-null objects returned by the + getRequestMessage and getResponseMessage methods of the MessageInfo are an instanceof + jakarta.xml.soap.SOAPMessage. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11344 The getSupportedMessageTypes method of all + authentication modules integrated for use with this profile, must include + jakarta.xml.soap.SOAPMessage.class in its return value. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11445 The CallbackHandler passed to an + authentication module's initialize method is determined by the handler argument passed in the call + to AuthConfigProvider.getClientAuthConfig or getServerAuthConfig that acquired the corresponding + authentication context configuration object. The handler argument must not be null, and the argument + handler and the CallbackHandler passed to the initialize method of an authentication modules should + support the following callbacks, and it must be possible to configure the runtime such that the + CallbackHandler passed at module initialization supports the following callbacks (in addition to any + others required to be supported by the applicable internal profile): CertStoreCallback, + PrivateKeyCallback, SecretKeyCallback, TrustStoreCallback true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11545 The CallbackHandler must be initialized with + any application context required to process the supported callbacks on behalf of the corresponding + application. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:11646 The factory implementation returned by + calling the getFactory method of the abstract AuthConfigFactory class must have been configured such + that it returns a non-null AuthConfigProvider for those application contexts for which pluggable + authentication modules have been configured at the SOAP layer. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11746 For each application context for which it is + servicing requests, the runtime must call getConfigProvider to acquire the provider object + corresponding to the layer and application context. The layer and appContext arguments to + getConfigProvider must be as defined in Section 4.1, Message Layer Identifier and Section 4.2, + Application Context Identifier respectively. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11846 A null return value from getConfigProvider + indicates that pluggable authentication modules have not been configured at the layer for the + application context and that the messaging runtime must proceed to perform its SOAP message + processing without reliance on this profile. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:11947 In cases where a runtime chooses to delegate + authentication session management to authentication contexts and their contained authentication + modules, the AuthConfigPrivider must have been configured, as described in Section 2.1.2.2, What the + Provider Must Do, to return non-null authentication contexts for all operation identifiers, + independent of whether or not the corresponding operation is protected. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:12047.1 If getOperation returns a non-null operation + identifier, then the operation identifier must be the String value corresponding to the operation + name appearing in the service description (i.e., WSDL). true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:12147.1 As defined in Section 2.1.3, “Acquire + AuthContext Identifier,” on page 17, the authentication context identifier used in the call to + getAuthContext must be equivalent to the value that would be acquired by calling getAuthContextID + with the MessageInfo that will be used in the corresponding call to secureRequest (by a client + runtime) or validateRequest (by a server runtime). true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:12247.2 Each authentication context object obtained + via getAuthContext must initialize its encapsulated authentication modules with a non-null + requestPolicy and/or a non-null responsePolicy; such that at least one of requestPolicy or + responsePolicy is not null. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12348.1 Unless the client runtime is embedded in a + server runtime (e.g.; an invocation of a web service by a servlet running in a Servlet container), + The CallbackHandler passed to ClientAuthModule.initialize must support the following callbacks: + NameCallback, PasswordCallback true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12448.2 If a non-null AuthConfigProvider is returned + (by the call to getConfigProvider), the messaging runtime must call getClientAuthConfig on the + provider to obtain the authentication context configuration object pertaining to the application + context at the layer. The layer and appContext arguments of the call to getClientAuthConfig must be + the same as those used to acquire the provider, and the handler argument must be as defined in + Section 4.8.1, ?CallbackHandler Requirements? for a client runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12548.3 If a non-null AuthConfigProvider is returned + (by the call to getConfigProvider), the messaging runtime must call getClientAuthConfig on the + provider to obtain the authentication context configuration object pertaining to the application + context at the layer. The layer and appContext arguments of the call to getClientAuthConfig must be + the same as those used to acquire the provider, and the handler argument must be as defined in + Section 4.8.2, CallbackHandler Requirements, for a client runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12648.3 A null return value from getAuthContext + indicates that pluggable authentication modules have not been configured for the operation within + the authentication context configuration scope, and that the client runtime must proceed to perform + its SOAP message processing without reliance on this profile. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12748.4.1 A non-null Subject corresponding to the + client must be passed as the clientSubject in the getAuthContext call. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:12848.4.2 A null value may be passed for the properties + argument in all calls made to getAuthContext true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:12948.4.3 Each ClientAuthContext obtained via + getAuthContext must initialize its encapsulated ClientAuthModule objects with requestPolicy and + responsePolicy objects (or null values) that are compatible with the requirements and capabilities + of the service invocation at the service. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13048.5 If the client runtime obtained a non-null + ClientAuthContext by using the operation identifier corresponding to the request message, then at + point (1) in the message processing model, the runtime must call secureRequest on the + ClientAuthContext, and at point (4) the runtime must call validateResponse on the ClientAuthContext. + + true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13148.4.1 The messageInfo argument used in a call to + secureRequest must have been initialized by the runtime such that its getRequestMessage will return + the SOAP request message being processed by the runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13248.5.1 When a corresponding call is made to + validateResponse, it must be made with the same messageInfo and clientSubject arguments used in the + corresponding call to secureRequest, and it must have been initiialized by the runtime such that its + getResponseMessage method will return the SOAP response message being processed by the runtime. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13348.5.1 This profile requires that the message + processing runtime establish the following key-value pairs within the Map of the MessageInfo passed + in the calls to secureRequest and validateResponse Key= jakarta.xml.ws.wsdl.service Value= qualified + service name, represented as a javax.xml.namespace.QName.. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13448.5.2 The clientSubject used in the call to + getAuthContext must be used in the call to secureRequest and for any corresponding calls to + validateResponse. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13548.5.3 When secureRequest is called on a module that + was initialized with a mandatory request policy (as defined by the return value from + requestPolicy.isMandatory()), the module must only return AuthStatus.SEND_SUCCESS if it was able to + completely satisfy the request policy. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:13648.5.3 If the module was not able to completely + satisfy the response policy, it must: return AuthStatus.SEND_CONTINUE - if it has established a + request (available to the runtime by calling messageInfo.getRequestMessage) that must be sent by the + runtime for the response validation to be effectively continued by the client. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13748.5.3 If the module was not able to completely + satisfy the response policy, it must: return AuthStatus.FAILURE - if the response validation failed. + The module must have established a response message containing a SOAP fault element (available to + the runtime by calling messageInfo.getResponseMessage) that may be returned to the application to + indicate that the request failed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13848.5.3 If the module was not able to completely + satisfy the response policy, it must: throw an AuthException - if the response validation failed. + The runtime may choose to return a response message containing a SOAP fault element, in which case, + the runtime must define the content of the message and of the fault, and may do so based on the + content of the AuthException. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:13948.5.3 When secureRequest is called on a module that + was initialized with an optional requestPolicy (i.e., requestPolicy.isMandatory() returns false), + the module should attempt to satisfy the request policy but it must do so without requiring + additional messages or interactions involving the service. Independent of whether the request policy + is satisfied, the module may return AuthStatus.SUCCESS. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14048.5.4 When validateResponse is called after the + service invocation on a module that was initialized with an undefined response policy (i.e., + responsePolicy == null), the module must return AuthStatus.SUCCESS. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14148.5.4 When validateResponse is called after the + service invocation on a module that was initialized with a mandatory response policy (as defined by + the return value from responsePolicy.isMandatory()), the module must only return AuthStatus.SUCCESS + if it was able to completely satisfy the response policy. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:14248.5.4 If the module was not able to completely + satisfy the response policy, it must: return AuthStatus.SEND_CONTINUE - if it has established a + request (available to the runtime by calling messageInfo.getRequestMessage) that must be sent by the + runtime for the response validation to be effectively continued by the client. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:14348.5.4 If the module was not able to completely + satisfy the response policy, it must: return AuthStatus.FAILURE - if the response validation failed. + The module must have established a response message containing a SOAP fault element (available to + the runtime by calling messageInfo.getResponseMessage) that may be returned to the application to + indicate that the request failed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14448.5.4 If the module was not able to completely + satisfy the response policy, it must: throw an AuthException - if the response validation failed. + The runtime may choose to return a response message containing a SOAP fault element, in which case, + the runtime must define the content of the message and of the fault, and may do so based on the + content of the AuthException. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14548.5.4 When validateResponse is called after the + service invocation on a module that was initialized with an optional responsePolicy (i.e., + responsePolicy.isMandatory() returns false), the module should attempt to satisfy the response + policy but it must do so without requiring additional messages or interactions involving the + service. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14648.5.4 Independent of whether the response policy is + satisfied, the module may return AuthStatus.SUCCESS. if the module determines that an invalid + security context was used to secure the response, then the module may return AuthStatus.FAILURE false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:14748.5.4 When validateResponse is called before the + service invocation, the module must return AuthStatus.SEND_CONTINUE if the request dialog is to + continue. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:14848.5.4 If the module returns AuthStatus.FAILURE, it + must have established a SOAP message containing a SOAP fault element as the response in messageInfo + and that may be returned to the application to indicate that the request failed. If the module + throws an AuthException, the runtime may choose to return a response message containing a SOAP fault + element, in which case, the runtime must define the content of the message and of the fault, and may + do so based on the content of the AuthException. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:14949.2 The CallbackHandler passed to + ServerAuthModule.initialize must support the following callbacks: CallerPrincipalCallback, + GroupPrincipalCallback , PasswordValidationCallback . true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15049.3 If a non-null AuthConfigProvider is returned + (by the call to getConfigProvider), the messaging runtime must call getServerAuthConfig on the + provider to obtain the authentication context configuration object pertaining to the application + context at the layer. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15149.3 A null return value from getAuthContext + indicates that pluggable authentication modules have not been configured for the operation at the + layer and for the application context and that the server runtime must proceed to perform its SOAP + message processing without reliance on this profile. true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:15249.3.1 A null value may be passed for the properties + argument in all calls made to getAuthContext true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:15349.4.2 When a non-null requestPolicy is used to + initialize the authentication modules of the ServerAuthContext must be constructed such that the + value obtained by calling isMandatory on the requestPolicy accurately reflects whether (i.e., true + return value) or not (i.e, false return value) message protection is required to access the web + service invocation corresponding to the MessageInfo used to acquire the ServerAuthContext. + Similarly, the responsePolicy used to initialize the authentication modules must be constructed such + that the value obtained by calling isMandatory on the responsePolicy accurately reflects whether + (i.e., true return value) or not (i.e, false return value) message protection is required (within + the SOAP messaging layer) on the response(if there is one) resulting from the corresponding + webservice invocation. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15449.4.2 Calling getTargetPolicies on the + requestPolicy corresponding to a web service invocation for which a SOAP layer client identity is to + be established as the caller identity must return an array containing at least one TargetPolicy for + which calling getProtectionPolicy.getID() returns one of the following values: + ProtectionPolicy.AUTHENTICATE_SENDER, ProtectionPolicy.AUTHENTICATE_CONTENT true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15549.5 If the server runtime obtained a non-null + ServerAuthContext by using the authentication context identifier corresponding to the request + message, then at point (2) in the message processing model, the runtime must call validateRequest on + the ServerAuthContext, and at point (3) the runtime must call secureResponse on the + ServerAuthContext. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15649.4 If the call to validateRequest returns + AuthStatus.SUCCESS, the runtime must perform any web service authorization processing2 required by + the runtime as a prerequisite to accessing the target resource. If authentication is required for + the request to be authorized, the runtime must determine whether the authentication identity + established in the clientSubject is authorized to access the resource. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15749.5 In a Jakarta Authorization compatible runtime, the identity + tested for authorization must be comprised of exactly the Principal objects of the clientSubject. If + the request is NOT authorized, and the message-exchange pattern is not one-way, the runtime must set + within the response (within messageInfo) a SOAP fault element as defined by the runtime. If the + request was determined to be authorized, it must be dispatched to the resource. Otherwise the + request must NOT be dispatched and the runtime must proceed to point (3) in the message processing + model (as appropriate to the message exchange pattern). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:15849.4 If the invocation of the resource results in + an exception being thrown by the resource to the runtime and the message exchange pattern is not + one-way, the runtime must set within the response (within messageInfo) a SOAP fault element as + defined by the runtime. Following the resource invocation, and if the message exchange pattern is + not one-way, the runtime must proceed to point (3) in the message processing model. At point (3) in + the message processing model, the runtime must call secureResponse on the same ServerAuthContext + used in the corresponding call to validateRequest and with the same MessageInfo object. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:15949.4 The call to secureResponse must not be made + if the resource throws an exception to the calling runtime. true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:16049.4 This profile requires that the message + processing runtime establish the following key-value pairs within the Map of the MessageInfo object + passed in the calls to validateRequest and secureResponse. Key= jakarta.xml.ws.wsdl.service value= + the application context identifier as defined in Sec 4.2 Application Context Identifier. true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:16149.5.2 A new clientSubject must be instantiated and + passed in any calls made to validateRequest. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:16249.5.3 When validateRequest is called before the + service invocation on a module that was initialized with an undefined request policy (i.e., + requestPolicy == null), the module must return AuthStatus.SUCCESS true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16349.5.3 When validateRequest is called before the + service invocation on a module initialized with a mandatory request policy (as defined by the return + value from requestPolicy.isMandatory()), the module must only return AuthStatus.SUCCESS if it was + able to completely satisfy the request policy. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16449.5.3 If the module returns AuthStatus.SUCCESS, and + the request policy was satisfied (and included a TargetPolicy element as described above), then the + module (or its context) must employ the CallerPrincipalCallback as described above. If the request + policy was not satisfied (and included a TargetPolicy element as described above), and yet the + module chooses to return AuthStatus.SUCCESS, the module (or its context) must use a + CallerPrincipalCallback to establish the container’s representation of the unauthenticated + caller within the clientSubject true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16549.5.3 If the module determines that an invalid or + incomplete security context was used to secure the request, then the module may return + AuthStatus.SEND_FAILURE, AuthStatus.SEND_CONTINUE, or throw an AuthException.If the module throws an + AuthException, or returns any value other that AuthStatus.SUCCESS, the runtime must NOT proceed to + the service invocation. The runtime must process an AuthException as described above for a request + with a mandatory requestPolicy. The runtime must process any return value other than + AuthStatus.SUCCESS as it would be processed if it were returned for a request with a mandatory + requestPolicy. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16649.5.3 If the module was not able to completely + satisfy the request policy, it must: return AuthStatus.SEND_FAILURE - if the request validation + failed, and when the module has established a SOAP message containing a fault element (available to + the runtime by calling messageInfo.getResponseMessage) that may be sent by the runtime to inform the + client that the request failed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16749.5.3 If the module was not able to completely + satisfy the request policy, it must: throw an AuthException - if the request validation failed, and + when the module has NOT defined a response, to be sent by the runtime. If the runtime chooses to + send a response, it must define a SOAP message containing a SOAP fault element, and may use the + content of the AuthException to do so. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16849.5.3 When validateRequest is called before the + service invocation on a module that was initialized with an optional request policy (i.e., + requestPolicy.isMandatory() returns false), the module should attempt to satisfy the request policy + but it must do so without requiring additional messages or interactions involving the client. If the + request policy is satisfied, and it included a TargetPolicy element with a PotectionPolicy of + AUTHENTICATE_SOURCE or AUTHENTICATE_CONTENT, then the module must employ the CallerPrincipalCallback + as described above. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:16949.4.3 Independent of whether the authentication + policy is satisfied, the module may return AuthStatus.SUCCESS. if the module determines that an + invalid security context was used to secure the request, or that the request requires additional + processing (e.g. decryption) to be suitable for processing by the runtime, then the module may + return AuthStatus.FAILURE or throw an AuthException. In which case, the runtime must determine + whether to terminate the request or to (attempt to) process it. true
+ 		falsetechnologydeprecatedfalse
JASPIC:SPEC:17049.5.3 When validateRequest is called after the + service invocation, the module must return AuthStatus.SEND_SUCCESS when the module has successfully + secured the application response message and made it available via messageInfo.getResponseMessage. + For the request to be successfully completed, the runtime must send the response message returned by + the module. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:17149.5.3 When securing of the application response + message has failed, and the response dialog is to be terminated, the module must return + AuthStatus.SEND_FAILURE or throw an AuthException. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:17249.5.3 If the module returns + AuthStatus.SEND_FAILURE, it must have established a SOAP message containing a SOAP fault element as + the response in messageInfo. The runtime may choose not to send a response message, or to send a + different response message. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:17349.5.3 When the module throws an AuthException, the + runtime may chose not to send a response. If the runtime sends a response, the runtime must define + the content of the response. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:17449.5.3 The module must return + AuthStatus.SEND_CONTINUE if the response dialog is to continue. This status value is used to inform + the calling runtime that (in order to successfully complete the response processing) it will need to + be capable of continuing the message dialog by processing at least one additional request/response + exchange (after having sent the response message returned in messageInfo). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:17549.5.4 When secureResponse is called on a module + that was initialized with an undefined responsePolicy (i.e., responsePolicy == null), the module + must return AuthStatus.SUCCESS. Otherwise, the AuthStatus return value and AuthException semantics + of secureResponse are as defined in validateRequest After Service Invocation. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:17651 The ServerAuthModule must create an instance + of a javax.security.auth.login.LoginContext. If the ServerAuthModule passes a custom + javax.security.auth.login.Configuration object to the constructor, then it also passes a custom + value as the name input. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:17751 If the ServerAuthModule does not pass a + custom Configuration object to the constructor, then it must pass its own fully qualified class name + as the name input. In this case, the configuration administrator must configure the relevant + LoginModule objects in an entry for that class name, or must configure the LoginModule objects into + the standard default entry called other. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:17851 If the ServerAuthModule passes a Subject to + the LoginContext constructor, it must pass its client Subject. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:17951 The ServerAuthModule must pass a + CallbackHandler to the constructor and the passed CallbackHandler must conform to the requirements + of Section 5.3, Standard Callbacks. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:18051 A new LoginContext instance should be created + for each new request, and a LoginContext instance should not be shared across different requests. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18151 Once a LoginContext object has been created, + the LoginContext.login method may be invoked from within the ServerAuthModule.validateRequest method + to delegate security processing to the LoginModule objects configured in the LoginContext. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18252 A LoginModule must only perform + protocolindependent security processing (for example, verifying a username/password that was + transmitted in the request). true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18352 A LoginModule requests information from the + ServerAuthModule using the ServerAuthModule provided CallbackHandler. Since the LoginModule must + only perform protocol-independent operations, it follows that any callback it requests from the + handler must also be protocol-independent. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18453 This profile requires that the + CallbackHandler provided by the ServerAuthModule to the LoginContext constructor support the + javax.security.auth.callback.NameCallback and the javax.security.auth.callback.PasswordCallback. + + true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:32653 If the ServerAuthModule passes its client + Subject to the LoginContext constructor, the CallbackHandler provided to the LoginContext + constructor must also support the GroupPrincipalCallback. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18554 If authentication succeeds, a LoginModule may + update its Subject instance with authenticated Principal and credential objects. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18654 If the ServerAuthModule did not pass its + client Subject to the LoginContext constructor, then it must transfer the Principals and credentials + from the LoginContext Subject to the client Subject. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:32754 If the ServerAuthModule is implementing a + profile of this specification that requires the module to employ the CallerPrincipalCallback, then + the ServerAuthModule must satisfy this requirement using the CallbackHandler provided to the + ServerAuthModule, and the CallerPrincipalCallback must be constructed using the name value that + would be obtained by the LoginModule if it uses its CallbackHandler to handle a NameCallback. (note + 1: The CallerPrincipalCallback may be constucted with a String argument containing the name value, + or with a Principal argument whose getName method returns the name value.) true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18755 When ServerAuthModule.cleanSubject is called + on the client Subject, the cleanSubject method must invoke the LoginContext.logout method. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18856 If the LoginContext instance throws a + LoginException, the ServerAuthModule must throw a corresponding AuthException. The LoginException + may be established as the cause of the AuthException. true
+ 		falsetechnologyactivefalse
JASPIC:SPEC:18961 The message layer value used to select the + AuthConfigProvider and ServerAuthConfig objects for this profile must be JMS false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19062 The application context identifier (i.e., the + appContext parameter value) used to select the AuthConfigProvider, ClientAuthConfig, and + ServerAuthConfig objects for a specific application shall be the name of the Destination. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19163 The MessageInfo argument used in any call + made by the message processing runtime to validateRequest or secureResponse must have been + initialized such that the non-null objects returned by the getRequestMessage and getResponseMessage + methods of the AuthParam are an instanceof javax.jmx.Message. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19264 The getSupportedMessageTypes method of all + authentication modules integrated for use with this profile, must include jakarta.jms.Message in its + return value. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19366 The factory implementation returned by + calling the getFactory method of the abstract AuthConfigFactory class must have been configured such + that it returns a non-null AuthConfigProvider for those application contexts for which pluggable + authentication modules have been configured at the JMS layer. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19466 For each JMS Destination for which it is + servicing requests, the runtime must call getConfigProvider to acquire the corresponding provider + object. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19566 For each JMS Destination for which it is + servicing requests, the runtime must call getConfigProvider to acquire the corresponding provider + object. The layer and appContext arguments to getConfigProvider must be as defined in Section 6.1, + 'Message Layer Identifier' and Section 6.2, 'Application Context Identifier' respectively. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19666 A null return value from getConfigProvider + indicates that pluggable authentication modules have not been configured at the layer for the + application context and that the messaging runtime must proceed to perform its JMS message + processing without reliance on this profile. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:19767 When a non-null AuthConfigProvider is + returned by the factory, the provider must have been configured with the information required to + initialize the authentication contexts for the (one or more) JMS Destinations for which the provider + is registered (at the factory). false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:19867.1 If getOperation returns a non-null operation + identifier, then the operation identifier must be the String value defined as follows: - When the + message is a request for a QueueConnection or a TopicConnection, then the operation identifier is + the String value representing the JNDI name of the Connection Factory. - When the message is a + request to create a publisher or subscriber, or a sender or receiver, then the operation identifier + must be the String value corresponding to the Destination name. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:19968 The following must be satisfied by a runtime + operating in the client role: A runtime may operate in both the client and server roles. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:20068.4.1 The messageInfo argument used in a call to + secureRequest must have been initialized by the runtime such that its getRequestMessage will return + the JMS request message being processed by the runtime. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:20168.4.1 When a corresponding call is made to + validateResponse, it must be made with the same messageInfo and clientSubject arguments used in the + corresponding call to secureRequest, and it must have been initialized by the runtime such that its + getResponseMessage method will return the JMS response message being processed by the runtime. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:20268.4.3 When secureRequest is called on a module that + was initialized with a mandatory request policy (as defined by the return value from + requestPolicy.isMandatory()), the module must only return AuthStatus.SEND_SUCCESS if it was able to + completely satisfy the request policy. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:20368.4.3 When secureRequest is called on a module that + was initialized with a mandatory request policy (as defined by the return value from + requestPolicy.isMandatory()), If the module was not able to completely satisfy the response policy, + it must: - return AuthStatus.SEND_CONTINUE - if it has established a request - return + AuthStatus.FAILURE - if the response validation failed. - throw an AuthException - if the response + validation failed. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:20468.4.3 When secureRequest is called on a module that + was initialized with an optional requestPolicy (i.e.,requestPolicy.isMandatory() returns false), if + the module attempts to satisfy the request policy, it must do so without requiring additional + messages or interactions involving the service. false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:20569 The requirements of this profile that must be + satisfied by a runtime operating in the server role are: - Receives a message from a Sender before + reaching the Queue - Receives a message from a Publisher on the way to a Topic - Receives a request + for creation of a TopicPublisher or QueueSender - Receives a message from the a JMS Provider false
+ 		falsetechnologyactivefalse
JASPIC:SPEC:20669.4.1 The messageInfo argument used in a call to + validateRequest must have been initialized by the runtime such that its getRequestMessage will + return the JMS request message being processed by the runtime. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:20769.4.1 When a corresponding call is made to + secureResponse, it must be made with the same messageInfo and serviceSubject arguments used in the + corresponding call to validateRequest, and it must have been initialized by the runtime such that + its getResponseMessage method will return the JMS response message being processed by the runtime. false
+ 		falsetechnologyactivetrue
JASPIC:SPEC:20848.1 The application context identifier used by a + client-runtime to acquire the AuthConfigProvider and ClientAuthConfig objects pertaining to the + client side processing of a web service invocation shall begin with a client scope identifier that + identifies the client. If the client-runtime may host multiple client applications, then the client + scope identifier must differentiate among the client applications deployed within the runtime. In + runtimes where applications are differentiated by unambiguous application identifiers, an + application identifier may be used as the client scope identifier. Where application identifiers are + not defined or suitable, the location (for example, its file path) of the client archive from which + the invocation will originate may be used as the client scope identifier In addition to its client + scope identifier, the application context identifier must include a client reference to the service. + If a service reference is defined for the invocation (for example, by using a WebServiceRef + annotation as defined in the JAXWS 2.0 or JAXWS 2.1 Specifications), the client reference to the + service must be the name value of the service reference. If a service reference was not defined for + the invocation, the client reference to the service must be the web service URL. A client + application context identifier must be the String value composed by concatenating the client scope + identifier, a blank separator character, and the client reference to the service. AppContextID ::= + client-scope-identfier blank client-reference true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:20949.1 The application context identifier used by a + server-runtime to acquire the AuthConfigProvider and ServerAuthConfig objects pertaining to the + endpoint side processing of an invocation shall be the String value constructed by concatenating a + host name, a blank separator character, and the path3 component of the service endpoint URI + corresponding to the webservice. AppContextID ::= hostname blank service-endpoint-uri In the + definition of server-side application context identifiers, this profile uses the term host name to + refer to the logical host that performs the service corresponding to a service invocation. Web + service invocations may be directed to a logical host using various physical or virtual host names + or addresses, and a message processing runtime may be composed of multiple logical hosts. Systems or + administrators that register AuthConfigProvider objects with specific server-side application + context identifiers must have an ability to determine the hostname for which they wish to perform + the registration. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:328PackageHead - + jakarta.security.auth.message.configAuthConfigFactory getConfigProvider(): All factories shall + employ the following precedence rules to select the registered AuthConfigProvider that matches the + layer and appContext arguments: 1. The provider that is specifically registered for both the + corresponding message layer and appContext shall be selected. 2. If no provider is selected + according to the preceding rule, the provider specifically registered for the corresponding + appContext and for all message layers shall be selected. 3. If no provider is selected according to + the preceding rules, the provider specifically registered for the corresponding message layer and + for all appContexts shall be selected. 4. If no provider is selected according to the preceding + rules, the provider registered for all message layers and for all appContexts shall be selected. 5. + If no provider is selected according to the preceding rules, the factory shall terminate its search + for a registered provider. The above precedence rules apply equivalently to registrations created + with a null or non-null className argument. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:329PackageHead - + jakarta.security.auth.message.configAuthConfigFactory getFactory(): If a non-null system-wide + factory instance is defined at the time of the call, for example, with setFactory, it will be + returned. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:330PackageHead - + jakarta.security.auth.message.configAuthConfigFactory getFactory(): The fully qualified class name + of the default factory implementation class is obtained from the value of the + authconfigprovider.factory security property. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:331PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(className, properties, + layer, appContext, description): At most one registration may exist within the factory for a given + combination of message layer and appContext. Any pre-existing registration with identical values for + layer and appContext is replaced by a subsequent registration. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:332PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(className, properties, + layer, appContext, description): [At most one registration may exist within the factory for a given + combination of message layer and appContext. Any pre-existing registration with identical values for + layer and appContext is replaced by a subsequent registration.] When replacement occurs, the + registration identifier, layer, and appContext identifier remain unchanged, and the + AuthConfigProvider (with initialization properties) and description are replaced. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:333PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(className, properties, + layer, appContext, description): Within the lifetime of its Java process, a factory must assign + unique registration identifiers to registrations, and must never assign a previously used + registration identifier to a registration whose message layer and or appContext identifier differ + from the previous use. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:334PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(provider, layer, + appContext, description): Registers within the (in-memory) factory, a provider of ServerAuthConfig + and/or ClientAuthConfig objects for a message layer and application context identifier. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:335PackageHead - + jakarta.security.auth.message.configAuthConfigFactory setFactory() Set the system-wide + AuthConfigFactory implementation. If an implementation was set previously, it will be replaced. + Listeners are not notified of a change to the registered factory. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:336PackageHead - + jakarta.security.auth.message.configAuthConfigFactory.RegistrationContext isPersistent() Returns: A boolean indicating + whether the registration is the result of a className based registration, or an instance-based (for + example, self-) registration. Only registrations performed using the five argument + registerConfigProvider method are persistent. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:33721.1.1 When a listener argument is included in the + call to acquire a provider, the factory will invoke the notify method of the listener when the + correspondence between the provider and the layer and application context for which is had been + acquired is no longer in effect. When the notify method is invoked by the factory, the runtime + should reacquire an AuthConfigProvider for the layer and application context. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:338PackageHead - + jakarta.security.auth.message.configRegistrationListener notify() The AuthConfigFactory will invoke + the notify method of the RegistrationListener if the corresponding provider registration is + unregistered or replaced at the factory. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:339PackageHead - + jakarta.security.auth.message.configAuthConfigFactory detachListener() The AuthConfigFactory will + invoke the notify method of the RegistrationListener if the corresponding provider registration is + unregistered or replaced at the factory. Returns: An array of String values where each value + identifies a provider registration from which the listener was removed. This method never returns + null; it returns an empty array if the listener was not removed from any registrations. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:340PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(className, properties, + layer, appContext, description) When replacement occurs, the registration identifier, layer, and + appContext identifier remain unchanged, and the AuthConfigProvider (with initialization properties) + and description are replaced. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:341PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(className, properties, + layer, appContext, description) Programmatic registrations performed by using this method must + update (according to the replacement rules described above) the persistent declarative + representation of provider registrations employed by the factory constructor. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:342PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(acp, layer, + appContext, description) At most one registration may exist within the factory for a given + combination of message layer and appContext. Any pre-existing registration with identical values for + layer and appContext is replaced by a subsequent registration. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:343PackageHead - + jakarta.security.auth.message.configAuthConfigFactory registerConfigProvider(acp, layer, + appContext, description) When replacement occurs, the registration identifier, layer, and appContext + identifier remain unchanged, and the AuthConfigProvider (with initialization properties) and + description are replaced. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:344PackageHead - + jakarta.security.auth.message.configAuthConfigFactory removeRegistration() Remove the identified + provider registration from the factory (and from the persistent declarative representation of + provider registrations, if appropriate) and invoke any listeners associated with the removed + registration. Verify this returns True when there is a registration with the specified identifier + and it was removed. true
+ 		falsetechnologyactivetrue
JASPIC:SPEC:345PackageHead - + jakarta.security.auth.message.configAuthConfigFactory removeRegistration() Remove the identified + provider registration from the factory (and from the persistent declarative representation of + provider registrations, if appropriate) and invoke any listeners associated with the removed + registration. Verify this returns false when the registrationID is invalid. true
+ 		falsetechnologyactivetrue
+ +