Configuration entry settings for JAAS

 

+

Search Tips   |   Advanced Search

 

Use this page to specify a list of JAAS login configurations for the application code to use, including J2EE components such as enterprise beans, JSP files, servlets, resource adapters, and message data blocks (MDBs).

To view this administrative console page, go to...

Click...

Security | Global security | JAAS configuration | Application logins

Read the JAAS specifications before you begin defining additional login modules for authenticating to the WAS security run time. You can define additional login configurations for your applications. However, if the WAS 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 WAS 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 install_root/properties directory. This configuration file is set in the /install_root/bin/launchClient.bat file as: set JAAS_LOGIN_CONFIG=-Djava.security.auth.login.config=%WAS_HOME%\properties\wsjaas_client.conf

If launchClient.bat file 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

ClientContainer

Specifies 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

DefaultPrincipalMapping

Specifies 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

WSLogin

Specifies whether all applications can use the WSLogin configuration to perform authentication for the WAS 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 WAS security run time. Use credentials from the authenticated subject returned from this login configurations as an authorization check for access to WAS resources.

Default: ClientContainer


 



 

 

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.