Web services security has the ability to send security tokens in the security header of a SOAP message. These security tokens can be used to sign, verify, encrypt or decrypt message parts. These security tokens can also be sent as standalone security tokens and set as the caller on the request consumer. Custom security token propagation is used to propagate these custom security tokens by using Web services security.
Web services security supports the Username, X.509 and Lightweight Third-Party Authentication (LTPA) security token types. When you use security token propagation, the propagation token is sent in the wsse:BinarySecurityToken element in the security header of the SOAP message. Web services security uses the same propagation token format as used by the Security attribute propagation feature. Configuring this option is similar to the configuration for sending and receiving LTPA tokens. The same token generator and token consumer implementations are used...
But, the token type Uniform Resource Identifier (URI) and local name for the token generator and token consumer are different. For custom token properties, use the following values:
By default, the custom token propagation uses the following JAAS login configuration entries:
You can use the com.ibm.ws.webservices.wssecurity.constants.jaasConfig
custom property to specify a different JAAS login configuration for the generator.
You can do this configuration on the CallbackHandler configuration panel.
To specify a different JAAS login configuration on the consumer side, use
the JAAS configuration name field in the Token consumer panel.