Login bindings configuration settings

 

+

Search Tips   |   Advanced Search

 

Use this page to configure the encryption and decryption parameters.

The pluggable token uses the JAAS CallBackHandler (javax.security.auth.callback.CallBackHandler) interface to generate the token that is inserted into the message. The following list describes the CallBack support implementations:

com.ibm.wsspi.wssecurity.auth.callback.BinaryTokenCallback

This implementation is used for generating binary tokens inserted as <wsse:BinarySecurityToken/@ValueType> in the message.

javax.security.auth.callback.NameCallback and javax.security.auth.callback.PasswordCallback

This implementation is used for generating user name tokens inserted as <wsse:UsernameToken> in the message.

com.ibm.wsspi.wssecurity.auth.callback.XMLTokenSenderCallback

This implementation is used to generate XML tokens and is inserted as the <SAML: Assertion> element in the message.

com.ibm.wsspi.wssecurity.auth.callback.PropertyCallback

This implementation is used to obtain properties that are specified in the binding file.

To view this administrative console page, complete the following steps:

  1. Click...

    Applications | Enterprise Applications | appname | EJB modules or Web modules | URI_file_name | Web Services: Client security bindings | Request Sender Bindings | Edit | Login binding

If the encryption information is not available, select None.

If the encryption information is available, select Dedicated login binding and specify the configuration in the following fields:

Authentication method

Specifies the unique name for the authentication method.

Uses any string to name the authentication method. However, the string must match the element in the server-level configuration. The following words are reserved by WAS:

BasicAuth

This method uses both a user name and a password.

IDAssertion

This method uses a user name, but it requires that additional trust is established by the receiving server using a trusted ID evaluator mechanism.

Signature

This method uses the distinguished name (DN) of the signer.

LTPA

This method validates the token.

Callback handler

Name of the callback handler. The callback handler must implement the javax.security.auth.callback.CallbackHandler interface.

Basic authentication user ID

Specifies the user name for basic authentication. With the basic authentication method, one can define a user name and a password in the binding file.

Basic authentication password

Specifies the password for basic authentication.

Token type URI

Namespace URI, which denotes the type of security token that is accepted.

The value of this field if is impacted by the following conditions:

  • 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.

  • The Token type URI field is ignored if the reserved words, which are listed in the description of the Authentication method field, are specified.

This information is inserted as <wsse:BinarySecurityToken>/ValueType for the <SAML: Assertion> XML token.

Token type local name

Specifies the local name of the security token type. For example, X509v3.

The value of this field if is impacted by the following conditions:

  • 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.

  • The Token type URI field is ignored if the reserved words, which are listed in the description of the Authentication method field, are specified.

This information is inserted as <wsse:BinarySecurityToken>/ValueType for the <SAML: Assertion> XML token.