JAAS configuration settings
Specify the name of the JAAS configuration defined in the JAAS login panel.
Complete the following steps to access this page on the cell level:
- Click Security > JAX-WS and JAX-RPC security runtime.
- Under JAX-RPC Default Consumer Bindings, click Token consumers > token_consumer_name or click New to create a new token consumer.
- Under Additional properties, click JAAS configuration.
Complete the following steps to access this page on the server level:
- Click Servers > Server Types > WebSphere application servers > server.
- Under Security, click security runtime.
Mixed-version environment: In a mixed node cell with a server using Websphere
Application Server version 6.1 or earlier, click Web services:
Default bindings for Web Services Security.mixv
- Under JAX-RPC Default Consumer Bindings, click Token consumers > token_consumer_name or click New to create a new token consumer.
- Under Additional properties, click JAAS configuration.
Complete the following steps to access this page on the application level:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security Properties, we can access the JAAS configuration settings for the following bindings:
- For the Response consumer (receiver) binding, click Web services: Client security bindings. Under Response consumer (receiver) binding, click Edit custom. Under Required properties, click Token consumers > token_consumer_name or click New to create a new token consumer. Under Additional properties, click JAAS configuration.
- For the Request consumer (receiver) binding, click Web services: Server security binding. Under Request consumer (receiver) binding, click Edit custom. Under Required properties, click Token consumers > token_consumer_name or click New to create a new token consumer. Under Additional properties, click JAAS configuration.
If we create a new token consumer, we must click Apply before proceeding to the JAAS configuration.
JAAS configuration name
Name of the JAAS system or application login configuration.
Do not remove the predefined system or application login configurations. However, within these configurations, we can add module class names and specify the order in which the application server loads each module.
Preconfigured system login configurations
The following predefined system login configurations are defined on the system logins panel, which is accessible by completing the following steps:
- Click Security > Global security.
- Expand Java Authentication and Authorization Service, click...
System logins.
- system.wssecurity.IDAssertionUsernameToken
- Enable a v6.x application to use identity assertion to map a user name to an application server credential principal.
- system.wssecurity.IDAssertion
- Enable an application to use identity assertion to map a user name to an application server credential principal.
- system.wssecurity.Signature
- Enable an application to map a distinguished name (DN) in a signed certificate to an application server credential principal.
- system.LTPA_WEB
- Processes login requests used by the web container such as servlets and JSP files.
- system.WEB_INBOUND
- Handles logins for web application requests, which include servlets and JSP files.
- system.RMI_INBOUND
- Handles logins for inbound Remote Method Invocation (RMI) requests.
- system.DEFAULT
- Handles the logins for inbound requests that are made by internal authentications and most of the other protocols ecept web applications and RMI requests.
- system.RMI_OUTBOUND
- Processes RMI requests sent outbound to another server
when either the com.ibm.CSI.rmiOutboundLoginEnabled or the com.ibm.CSIOutboundPropagationEnabled
properties are true. These properties are set in the Common Secure Interoperability v2 (CSIv2) authentication panel.
To access the panel, click Security > Global security. Epand RMI/IIOP security, click CSIv2 Outbound authentication. To set the com.ibm.CSI.rmiOutboundLoginEnabled property, select the Custom outbound mapping option. To set the com.ibm.CSIOutboundPropagationEnabled property, select the Security attribute propagation option.
- system.wssecurity.509BST
- Verifies an .509 binary security token (BST) by checking the validity of the certificate and the certificate path.
- system.wssecurity.PKCS7
- Verifies an .509 certificate with a certificate revocation list in a Public Key Cryptography Standards #7 (PKCS7) object.
- system.wssecurity.PkiPath
- Verifies an .509 certificate with a public key infrastructure (PKI) path.
- system.wssecurity.UsernameToken
- Verifies basic authentication (user name and password).
Application login configurations
The following predefined application login configurations are defined on the Application logins panel, which is accessible by completing the following steps:
- Click Security > Global security.
- Expand Java Authentication and Authorization Service, click Application logins.
- ClientContainer
- Login configuration used by the client container application. This application uses the CallbackHandler API defined in the deployment descriptor of the client container.
- WSLogin
- Specifies whether all applications can use the WSLogin configuration to perform authentication for the application server security run time.
- DefaultPrincipalMapping
- Specifies the login configuration used by Java 2 Connectors (J2C) to map users to principals defined in the J2C authentication data entries.