Actions Of Request And Response Policy Configurations; Message Protection Policy To Ws-Security Soap Message Security Operation Mapping - Sun Microsystems GlassFish Enterprise Server 2.1 Administration Manual

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 WS-Security SOAP message security providers for that
configuration.
TABLE 10–1
Message Protection Policy
auth-source="sender"
auth-source="content"
auth-source="sender"
auth-recipient="before-content"
OR
auth-recipient="after-content"
auth-source="content"
auth-recipient="before-content"
auth-source="content"
auth-recipient="after-content"
134 Sun GlassFish Enterprise Server 2.1 Administration Guide • December 2008

Message protection policy to WS-Security SOAP message security operation mapping

Resulting WS-Security SOAP message protection operations
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
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.