
Configuring the Enterprise Server for Message Security
TABLE
(Continued)
Message Protection Policy | Resulting | |
|
| |
The content of the SOAP message Body is encrypted and | ||
OR | 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. |
No policy specified.
No security operations are performed by the modules.
Configuring Other Security Facilities
The Enterprise Server implements message security using message security providers integrated in its SOAP processing layer. The message security providers depend on other security facilities of Enterprise Server.
1.If using a version of the Java SDK prior to version 1.5.0, and using encryption technology, configure a JCE provider.
2.Configuring a JCE provider is discussed in “Configuring a JCE Provider” on page 135.
3.If using a username token, configure a user database, if necessary. When using a username/password token, an appropriate realm must be configured and an appropriate user database must be configured for the realm.
4.Manage certificates and private keys, if necessary.
After You Finish
Once the facilities of the Enterprise Server are configured for use by message security providers, then the providers installed with the Enterprise Server may be enabled as described in “Enabling Providers for Message Security” on page 137.
Configuring a JCE Provider
The Java Cryptography Extension (JCE) provider included with J2SE 1.4.x does not support RSA encryption. Because the XML Encryption defined by
Note – RSA is
Chapter 10 • Configuring Message Security | 135 |