Login mapping configuration settings

 

+

Search Tips   |   Advanced Search

 

Use this page to specify the Java Authentication and Authorization Service (JAAS) login configuration settings that are used to validate security tokens within incoming messages.

There is an important distinction between V5.x and V6 and later applications. The information in this article supports V5.x applications only that are used with WAS V6.0.x and later. The information does not apply to V6.0.x and later applications.

To view this console page for the cell level...

  1. Click...

      Security | Web services | Additional properties | Login mappings

  2. Click either New to create a new login mapping configuration or click the name of an existing configuration.

To view this console page for the server level, complete the following steps:

  1. Click...

      Servers | Application servers | server | Security | Web services: Default bindings for Web services security | Additional properties | Login mappings

  2. Click either New to create a new login mapping configuration or click the name of an existing configuration.

To use this console page for the application level, complete the following steps:

  1. Click...

      Applications | Enterprise applications | application | Modules | Manage modules | URI_name | Web Services Security Properties | Web services: Server security bindings | Request receiver binding | Edit | Login mappings

  2. Click either New to create a new login mapping configuration or click the name of an existing configuration.

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. If the configuration is not found on the server level, the Web services run time searches the cell.

Authentication method

[V5 only]

Method of authentication.

You can use any string, but the string must match the element in the service-level configuration. The following words are reserved and have special meanings:

BasicAuth

Uses both a user name and a password.

IDAssertion

Uses only a user name, but requires that additional trust is established on the receiving server using a TrustedIDEvaluator mechanism.

Signature

Uses the distinguished name (DN) of the signer.

LTPA

Validates a token.

JAAS configuration name

[V5 only]

Name of the Java Authentication and Authorization Service (JAAS) configuration.

You can use the following predefined system login configurations:

system.wssecurity.IDAssertion

Enables a version 5.x application to use identity assertion to map a user name to a WAS credential principal.

system.wssecurity.Signature

Enables a version 5.x application to map a distinguished name (DN) in a signed certificate to a WAS credential principal.

system.LTPA_WEB

Processes login requests that are used by the Web container such as servlets and JavaServer Pages files.

system.WEB_INBOUND

Handles logins for Web application requests, which include servlets and JavaServer Pages. This login configuration is used by WebSphere Application Server V5.1.1.

system.RMI_INBOUND

Handles logins for inbound RMI requests. This login configuration is used by WAS V5.1.1.

system.DEFAULT

Handles the logins for inbound requests made by internal authentications and most of the other protocols except Web applications and RMI requests.

This login configuration is used by WAS V5.1.1.

system.RMI_OUTBOUND

Processes RMI requests that are sent outbound to another server when the com.ibm.CSIOutboundPropagationEnabled property is true.

This property is set in the CSIv2 authentication panel. To access the panel, click...

    Security | Secure administration, applications, and infrastructure | RMI/IIOP security | CSIv2 Outbound authentication

To set the com.ibm.CSIOutboundPropagationEnabled property, select Security attribute propagation.

system.wssecurity.X509BST

[V6 only]

Verifies an X.509 binary security token (BST) by checking the validity of the certificate and the certificate path.

system.wssecurity.PKCS7

[V6 only]

Verifies an X.509 certificate with a certificate revocation list in a PKCS7 object.

system.wssecurity.PkiPath

[V6 only]

Verifies an X.509 certificate with a public key infrastructure (PKI) path.

system.wssecurity.UsernameToken

[V6 only]

Verifies basic authentication (user name and password).

These system login configurations are defined on the System logins panel, which is accessible by completing the following steps:

  1. Click...

The predefined system login configurations are listed on the System logins configuration panel without the system prefix. For example, the system.wssecurity.UsernameToken configuration listed in the JAAS configuration name option corresponds to the wssecurity.UsernameToken configuration that is on the System logins configuration panel.

You can use the following predefined application login configurations:

ClientContainer

Login configuration that is used by the client container application, which uses the CallbackHandler API that is defined in the deployment descriptor of the client container.

WSLogin

Specifies whether all applications can use the WSLogin configuration to perform authentication for the WAS security run time.

DefaultPrincipalMapping

Login configuration used by Java 2 Connectors (J2C) to map users to principals that are defined in the J2C authentication data entries.

These application login configurations are defined on the Application logins panel, which is accessible by completing the following steps:

  1. Click...

Do not remove these predefined system or application login configurations. Within these configurations, you can add module class names and specify the order in which WAS loads each module.

Callback handler factory class name

[V5 only]

Name of the factory for the CallbackHandler class.

Implement the com.ibm.wsspi.wssecurity.auth.callback.CallbackHandlerFactory class in this field.

Token type URI

[V5 only]

Namespace Uniform Resource Identifiers (URI), which denotes the type of security token that is accepted.

If binary security tokens are accepted, the value denotes the ValueType attribute in the element. The ValueType element identifies the type of security token and its namespace. If XML tokens are accepted, the value denotes the top-level element name of the XML token.

If the reserved words are specified previously in the Authentication method field, this field is ignored.

Data type: Unicode characters except for non-ASCII characters, but including the number sign (#), the percent sign (%), and the square brackets ([ ]).

Token type local name

[V5 only]

Local name of the security token type, for example, X509v3.

If binary security tokens are accepted, the value denotes the ValueType attribute in the element. The ValueType attribute identifies the type of security token and its namespace. If XML tokens are accepted, the value denotes the top-level element name of the XML token.

If the reserved words are specified previously in the Authentication method field, this field is ignored.

Nonce maximum age

[V5 only]

Timeime, in seconds, before the nonce timestamp expires. Nonce is a randomly generated value.

You must specify a minimum of 300 seconds for the Nonce maximum age field. However, the maximum value cannot exceed the number of seconds specified in the Nonce cache timeout field for either the server level or the cell level.

You can specify the Nonce maximum age value for the cell level by completing the following steps:

  1. Click Security > Web services.

You can specify the Nonce maximum age value for the server level by completing the following steps:

  1. Click...

      Servers | Application Servers | server | Security | Web Services: Default bindings for Web Services Security

The Nonce maximum age field on this panel is optional and only valid if the BasicAuth authentication method is specified. If you specify another authentication method and attempt to specify values for this field, the following error message displays and remove the specified value: Nonce is not supported for authentication methods other than BasicAuth.

If you specify the BasicAuth method, but do not specify values for the Nonce maximum age field, the Web services security run time searches for a Nonce maximum age value on the server level. If a value is not found on the server level, the run time searches the cell level. If a value is not found on either the server level or the cell level, the default is 300 seconds.

Default 300 seconds
Range 300 to Nonce cache timeout seconds

Nonce clock skew

[V5 only]

Specify the clock skew value, in seconds, to consider when WebSphere Application Server checks the freshness of the message. Nonce is a randomly generated value.

You can specify the Nonce clock skew value for the cell level by completing the following steps:

  1. Click Security > Web services.

You can specify the Nonce clock skew value for the server level by completing the following steps:

  1. Click...

      Servers | Application Servers | server | Security | Web Services: Default bindings for Web Services Security

You must specify a minimum of zero (0) seconds for the Nonce Clock Skew field. However, the maximum value cannot exceed the number of seconds that is specified in the Nonce maximum age field on this Login mappings panel.

The Nonce clock skew field on this panel is optional and only valid if the BasicAuth authentication method is specified. If you specify another authentication method and attempt to specify values for this field, the following error message displays and remove the specified value: Nonce is not supported for authentication methods other than BasicAuth.

If you specify BasicAuth, but do not specify values for the Nonce clock skew field, WAS searches for a Nonce clock skew value on the server level. If a value is not found on the server level, the run time searches the cell level. If a value is not found on either the server level or the cell level, the default is zero (0) seconds.

Default 0 seconds
Range 0 to Nonce Maximum Age seconds



 

Related concepts

Login mappings

 

Related tasks

Securing Web services for V5.x applications using XML digital signature

 

Related Reference

Login mappings collection
Default bindings for Web services security