WAS v8.5 > Reference > SetsLogin mappings page
Use this page to view a list of configurations for validating security tokens within incoming messages. Login mappings map an authentication method to a JAAS login configuration to validate the security token. Four authentication methods are predefined in the WebSphere Application Server: BasicAuth, Signature, IDAssertion, and LTPA.
There is an important distinction between v5.x and v6 and later applications. The information in this article supports v5.x applications only used with WAS v6.0.x and later. The information does not apply to v6.0.x and later applications. v5.x applications are based on Java 2 platform, Enterprise Edition (J2EE) 1.3.
To view this dmgr console page for the server level...
- Click Servers > Server Types > WebSphere application servers > server_name.
- Under Security, click JAX-WS and JAX-RPC security runtime.
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.
- Under Additional properties, click Login mappings.
- Click either New to create a new login mapping configuration or click the name of an existing configuration.
To view this dmgr console page for the application level...
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_name.
- Under Web Services Security properties, click Web services: Server security bindings.
- Click Edit under Request receiver binding.
- Click Login mappings.
If you click Update runtime, the Web Services Security run time is updated with the default binding information, which is contained in the ws-security.xml file that was previously saved. After we specify the authentication method, the JAAS configuration name, and the Callback Handler Factory class name on this panel, you must complete the following steps:
- Click Save in the messages section at the top of the dmgr console.
- Click Update runtime. When you click Update runtime, the configuration changes made to the other web services also are updated in the Web Services Security run time.
If the login mapping configuration is not found on the application level, the web services run time searches for the login mapping configuration on the server level.
Authentication method
Authentication method used for validating the security tokens.
The following authentication methods are available:
- BasicAuth
- The basic authentication method includes both a user name and a password in the security token. The information in the token is authenticated by the receiving server and is used to create a credential.
- Signature
- The signature authentication method sends an X.509 certificate as a security token. For LDAP registries, the distinguished name (DN) is mapped to a credential, which is based on the LDAP certificate filter settings. For local OS registries, the first attribute of the certificate, usually the common name (CN) is mapped directly to a user name in the registry.
- IDAssertion
- The identity assertion method maps a trusted identity (ID) to a WAS credential. This authentication method only includes a user name in the security token. An additional token is included in the message for trust purposes. When the additional token is trusted, the IDAssertion token user name is mapped to a credential.
- LTPA
- Lightweight Third Party Authentication (LTPA) validates an LTPA token.
JAAS configuration name
Name of the JAAS configuration.
Callback handler factory class name
Name of the factory for the CallbackHandler class.
Related concepts:
BasicAuth authentication method
Identity assertion authentication method
Signature authentication method
LTPA
Related
Secure web services for v5.x applications using XML digital signature
Reference:
Login mapping configuration settings