Configuration entry settings for Java Authentication and Authorization Service
Use this page to specify a list of Java™ Authentication and Authorization Service (JAAS) login configurations for the application code to use, including Java Platform, Enterprise Edition (Java EE) components such as enterprise beans, JavaServer Pages (JSP) files, servlets, resource adapters, and message-driven beans (MDBs).
- Click Security > Global security.
- Under Authentication, click Java Authentication and Authorization Service > Application logins.
Read the JAAS specifications before you begin defining additional login modules for authenticating to the application server security run time. You can define additional login configurations for your applications. However, if the application server LoginModule com.ibm.ws.security.common.auth.module.WSLoginModuleImpl module is not used or the LoginModule module does not produce a credential that is recognized by the application server. The application server security run time cannot use the authenticated subject from these login configurations for an authorization check for resource access.
You must invoke Java client programs that use Java Authentication and Authorization Service (JAAS) for authentication with a JAAS configuration file that is specified.
![[AIX Solaris HP-UX Linux Windows]](../images/ngdist.svg)
![[z/OS]](../images/ngzos.svg)
The application server supplies the wsjaas_client.conf
default JAAS configuration file under the app_server_root/properties
directory. This configuration file is set in the
app_server_root/bin/launchClient.bat file as:
set JAAS_LOGIN_CONFIG=-Djava.security.auth.login.config=%app_server_root%\properties\wsjaas_client.conf
![[IBM i]](../images/ngibmi.svg)
The application server supplies the default JAAS configuration file in the
profile_root/properties/wsjaas_client.conf file.
This configuration file is set in the launchClient Qshell script.
ClientContainer
Specifies the login configuration used by the client container application, which uses the CallbackHandler API that is defined in the client container deployment descriptor.
The ClientContainer configuration is the default login configuration for the application server. Do not remove this default, as other applications that use it fail.
| Information | Value |
|---|---|
| Default: | ClientContainer |
DefaultPrincipalMapping
Specifies the login configuration that is used by Java 2 Connectors to map users to principals that are defined in the J2C authentication data entries.
The ClientContainer configuration is the default login configuration for the application server. Do not remove this default, as other applications that use it fail.
| Information | Value |
|---|---|
| Default: | ClientContainer |
WSLogin
Indicates whether all of the applications can use the WSLogin configuration to perform authentication for the application server security run time.
This login configuration does not honor the CallbackHandler handler that is 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 application server. Do not remove this default because other administrative applications that use it fail. This login configuration authenticates users for the application server security run time. Use the credentials from the authenticated subject that are returned from this login configuration as an authorization check for access to application server resources.
| Information | Value |
|---|---|
| Default: | ClientContainer |