Login module settings for Java Authentication and Authorization ServiceUse this page to define the login module for a Java Authentication and Authorization Service (JAAS) login configuration.
To view this administrative
page, click Security > JAAS Configuration > Application Logins > alias_name > JAAS
Login Modules.
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:
| Data type: | String |
![[Version 5.1.1 and later]](v511x.gif)
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 WebSphere 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 WebSphere Application Server product class loaders.
| Data type: | String |
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 |
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.
![[Version 5.1.1 and later]](v511x.gif)
Click Set Order to change the processing order of the login modules.