controlFlag Attribute Values

The SAP implementation uses the same control flag (controlFlag) attribute values and definitions as those defined in the JAAS specification.

If you stack multiple providers, you must set the control flag attribute for each enabled provider.

Control Flag Value	Description
Required	The authentication provider is required. Authentication proceeds down the authentication provider list.
Requisite	The authentication provider is required. Subsequent behavior depends on the authentication result: If authentication succeeds, authentication continues down the authentication provider list. If authentication fails, control returns immediately to the application (authentication does not proceed down the authentication provider list).
Sufficient	The authentication provider is not required. Subsequent behavior depends on the authentication result: If authentication succeeds, control returns immediately to the application (authentication does not proceed down the authentication provider list). If authentication fails, authentication continues down the authentication provider list.
Optional (default)	The authentication provider is not required to successfully authenticate the user. Regardless of success or failure, authentication proceeds down the authentication provider list.

Example

Providers are listed in this order and with these controlFlag settings:

X.509 User Certificate (sufficient)
Directory Service (LDAP/AD) (optional)
HTTP/HTTPS Authentication (sufficient)

A client performing certificate authentication (for example, X.509 SSO to SAP) can authenticate immediately. Subsequent providers are not called, because they are not required. Regular user name and password credentials, if they exist, go to LDAP, which may authenticate them, and set them up with roles from the LDAP groups they belong to. Then NativeOS is invoked, and if that succeeds, SAP Mobile Platform picks up roles based on the Windows groups they belong to.