Use this page to specify a list of Java Authentication and Authorization Service (JAAS) login configurations for the application code to use, including J2EE artifacts such as enterprise beans, JavaServer Pages (JSP) files, servlets, resource adapters, and message data blocks (MDBs). To view this administrative console page, complete the following steps:
Read the JAAS documentation before you begin defining additional login modules for authenticating to the WebSphere Application Server security run time. You can define additional login configurations for your applications. However, if the WebSphere Application Server LoginModule (com.ibm.ws.security.common.auth.module.WSLoginModuleImpl) is not used or the LoginModule does not produce a credential that is recognized by WebSphere Application Server, then the WebSphere Application Server security run time cannot use the authenticated subject from these login configurations for an authorization check for resource access.
Note: You must invoke Java client programs that use Java Authentication and Authorization Service (JAAS) for authentication with a JAAS configuration file specified. The WebSphere product supplies the default JAAS configuration file, wsjaas_client.conf under the profile_root/properties directory, where profile_root is the directory that contains your profile. In the default installation, profile_root is /QIBM/UserData/WebSphere/AppServer/V6/edition/profiles. This configuration file is set in the launchClient Qshell script.
If the launchClient script is not used to invoke Java client programs, make sure that the appropriate
JAAS configuration file is passed to the Java virtual machine with the -Djava.security.auth.login.config flag.
Configuration tab
The login configuration used by the client container application, which uses the CallbackHandler API defined in the client container deployment descriptor.
The ClientContainer configuration is the default login configuration for the WebSphere Application Server. Do not remove this default, as other applications that use it fail.
| Default: | ClientContainer |
The login configuration used by Java 2 Connectors to map users to principals that are defined in the J2C Authentication Data Entries.
ClientContainer is the default login configuration for the WebSphere Application Server. Do not remove this default, as other applications that use it fail.
| Default: | ClientContainer |
Whether all applications can use the WSLogin configuration to perform authentication for the WebSphere Application Server security run time.
This login configuration does not honor the CallbackHandler defined in the client container deployment descriptor. To use this functionality, use the ClientContainer login configuration.
The WSLogin configuration is the default login configuration for the WebSphere Application Server. Do not remove this default because other administrative
applications that use it will fail. This login configuration authenticates users for the WebSphere Application Server security run time. Use credentials from the authenticated subject returned from this login configurations as an authorization check for access to WebSphere Application Server resources.
| Default: | ClientContainer |
Related concepts
Java Authentication and Authorization Service
Related reference
Administrative console buttons
Administrative console page features
Administrative console scope settings
Administrative console preference settings