Login module settings for Java Authentication and Authorization Service

Use this page to define the login module for a Java Authentication and Authorization Service (JAAS) login configuration. You can define the JAAS login modules for application and system logins. To define these login modules in the administrative console, complete the following steps:

Click Security > Global security.
Under Authentication, click JAAS configuration > Application logins or System logins > alias_name.
Under Additional properties, click JAAS login modules.

Module class name

The class name of the given login module.

Data type: String

Use login module proxy

That the Java Authentication and Authorization Service (JAAS) loads the login module proxy class. JAAS then delegates calls to the login module classes that are defined in the Module class name field.

Use this option when you use both Version 5.x and Version 6 Application Servers in the same environment. If you migrate a Version 5.x Application Server to Version 6, WebSphere Application Server Version 6 automatically enables this option. If you have Version 6 only cells in your environment, you might choose to deselect this option.

Default: Enabled

Proxy class name

The name of the proxy login module class.

The default login modules that are defined by the application server use the com.ibm.ws.security.common.auth.module.WSLoginModuleProxy proxy LoginModule class. This proxy class loads the application server login module with the thread context class loader and delegates all the operations to the real login module implementation. The real login module implementation is specified as the delegate option in the option configuration. The proxy class is needed because the Developer Kit application class loaders do not have visibility of the application server product class loaders.

Data type: String

Authentication strategy

The authentication behavior as authentication proceeds down the list of login modules.

A Java Authentication and Authorization Service (JAAS) authentication provider supplies the authentication strategy. In JAAS, an authentication strategy is implemented through the LoginModule interface.

Data type: String
Default: Required
Range: Required, Requisite, Sufficient and Optional

Required: The LoginModule module is required to succeed. Whether authentication succeeds or fails, the process still continues down the LoginModule list for each realm.
Requisite: The LoginModule module is required to succeed. If authentication is successful, the process continues down the LoginModule list in the realm entry. If authentication fails, control immediately returns to the application. Authentication does not proceed down the LoginModule list.
Sufficient: The LoginModule module is not required to succeed. If authentication succeeds, control immediately returns to the application. Authentication does not proceed down the LoginModule list. If authentication fails, the process continues down the list.
Optional: The LoginModule module is not required to succeed. Whether authentication succeeds or fails, the process still continues down the LoginModule list.

Specify additional options by clicking Custom Properties under Additional Properties. These name and value pairs are passed to the login modules during initialization. This process is one of the mechanisms that is used to passed information to login modules.

Module order

The order in which the Java Authentication and Authorization Service (JAAS) login modules are processed.

Click Set Order to change the processing order of the login modules.

Data type:	String
Default:	Required
Range:	Required, Requisite, Sufficient and Optional

Login module settings for Java Authentication and Authorization Service

Related tasks