en.help.ref-configreq-respolicy.html Maven / Gradle / Ivy

Go to download

Show more of this group Show more artifacts with this name
Show all versions of console-common-help

Online help content for the console-common bundle.

There is a newer version: 3.2-b03


Request and Response Policy Configurations
If Authenticate Source is sender, then the message contains a wsse:Security header with
a wsse:UsernameToken (with password). If Authenticate Source is content, then the content of
the SOAP message body is signed, and the message contains a wsse:Security
header with the message body signature represented as a ds:Signature.

If Authenticate Recipient is either before-content or after-content, 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 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.

If the Authenticate Source and Authenticate Recipient settings are left blank, then no
security policy is specified, and the modules perform no security operations.

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 1 Message Protection Policy Based on WS-Security Soap Message Security Operation

Authenticate Recipient
before-content


Authenticate Recipient after-content



Authenticate Source sender


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.



Authenticate Source content


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.





Copyright © 2005, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices

	Authenticate Recipient `before-content`	Authenticate Recipient `after-content`
Authenticate Source `sender`	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.
Authenticate Source `content`	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.