Use this page to configure the encryption and decryption parameters.
Important: There is an important distinction between Version 5.x and
Version 6 and later applications. The information in this article supports
Version 5.x applications only that are used with WebSphere® Application
Server Version 6.0.x and later. The information does not apply to Version
6.0.x and later applications.
The pluggable token uses the Java™ Authentication and Authorization Service
(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 that are specified in
the binding file.
To view this administrative console page, complete the following steps:
- Click 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: