Configuring the Enterprise Server for Message Security
Actions of Request and Response Policy
Configurations
The following table shows message protection policy configurations and the resulting message security operations performed by the
TABLE
Message Protection Policy | Resulting | |
|
| |
The message contains a wsse:Security header that | ||
| contains a wsse:UsernameToken (with password). | |
|
| |
The content of the SOAP message Body is signed. The | ||
| message contains a wsse:Security header that contains | |
| the message Body signature represented as a | |
| ds:Signature. | |
|
| |
The content of the SOAP message Body is encrypted and | ||
replaced with the resulting xend:EncryptedData. The | ||
message contains a wsse:Security header that contains | ||
| ||
OR | a wsse:UsernameToken (with password) and an | |
xenc:EncryptedKey. The xenc:EncryptedKey contains | ||
the key used to encrypt the SOAP message body. The key | ||
| is encrypted in the public key of the recipient. | |
|
| |
The content of the SOAP message Body is encrypted and | ||
replaced with the resulting xend:EncryptedData. The | ||
xenc:EncryptedData is signed. The message contains a | ||
| ||
| wsse:Security header that contains an | |
| xenc:EncryptedKey and a ds:Signature. The | |
| xenc:EncryptedKey contains the key used to encrypt the | |
| SOAP message body. The key is encrypted in the public | |
| key of the recipient. | |
|
| |
The content of the SOAP message Body is signed, then | ||
encrypted, and then replaced with the resulting | ||
xend:EncryptedData. The message contains a | ||
| ||
| wsse:Security header that contains an | |
| xenc:EncryptedKey and a ds:Signature. The | |
| xenc:EncryptedKey contains the key used to encrypt the | |
| SOAP message body. The key is encrypted in the public | |
| key of the recipient. | |
|
|
134 | Sun GlassFish Enterprise Server 2.1 Administration Guide • December 2008 |