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, use one of the following paths:
- To view this administrative console page, 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
Specifies the class name of the given login module.
Data type: String
- Proxy class name
Name of the proxy login module class.
The default login modules defined by the WebSphere product use the proxy LoginModule class, com.ibm.ws.security.common.auth.module.WSLoginModuleProxy. This proxy class loads the WAS 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 WAS product class loaders.
Data type: String
- Authentication Strategy
Specifies the authentication behavior as authentication proceeds down the list of login modules.
A 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
- The LoginModule is required to succeed. If it succeeds or fails, authentication still continues to proceed down the LoginModule list for each realm.
- The LoginModule is required to succeed. If it succeeds, authentication continues down the LoginModule list in the realm entry. If it fails, control immediately returns to the application--that is, authentication does not proceed down the LoginModule list.
- The LoginModule is not required to succeed. If it does succeed, control immediately returns to the application--again, authentication does not proceed down the LoginModule list. If it fails, authentication continues down the list.
- The LoginModule is not required to succeed. If it succeeds or fails, authentication still continues to proceed 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
Specifies 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.
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.