Login bindings configuration settings
Specify the JAAS login configuration settings used to validate security tokens within incoming messages.
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 Extensible Markup Language (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 specified in the binding file.
To view this administrative console page:
- Click Applications > Application Types > WebSphere enterprise applications > application_name.
- Under Modules, click Manage modules > URI_file_name. Under Web Services Security Properties, click Web Services: Client security bindings.
- Under Request Sender Bindings, click Edit.
- Under Additional properties, click 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
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
User name for basic authentication. With the basic authentication method, we can define a user name and a password in the binding file.
Basic authentication password
Password for basic authentication.
Token type URI
Namespace Uniform Resource Identifiers (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
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.
Secure web services for v5.x applications using XML encryption