You can configure responses to produce any type of WS-Security token upon successful authorization of a request. However, not every authentication scheme gathers all the necessary information (username, clear text password, SOAP message) from an incoming request to create every type of token.
If a response is configured to create a token that requires anything that the configured authentication scheme does not provide, header creation fails. Verify that the authentication method that you plan to use is suitable to produce the WS-Security token that you want to produce in response.
The following table shows which WS-Security tokens can be produced for each authentication method.
|
|
|
WS-Security Token Types That Can be Produced |
|||
|---|---|---|---|---|---|
|
Authentication Method |
|
Username and Password |
Username and Password Digest |
SAML |
X.509 |
|
Basic (SOA Agent for Web Servers only) |
|
No |
Yes |
No |
No |
|
XML-DCC |
|
Yes |
Yes |
Yes |
Yes |
|
XML-DSIG |
|
No |
No |
Yes |
Yes |
|
SAML Session Ticket |
|
No |
No |
Yes |
Yes |
|
WS-Security Username and Password Token |
|
Yes |
Yes |
Yes |
Yes |
|
WS-Security Username and Password Digest Token |
|
No |
Yes |
Yes |
Yes |
|
WS-Security SAML Token |
|
No |
No |
Yes |
Yes |
|
WS-Security X.509 Token |
|
No |
No |
Yes |
Yes |
|
SiteMinder Session (SMSESSION) Cookie |
|
No |
No |
No |
No |
| Copyright © 2011 CA. All rights reserved. | Email CA Technologies about this topic |