From 012d23e05f342412503fc6f91082b9d245b1a308 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Thu, 28 Feb 2008 16:24:10 +0000 Subject: [PATCH] SWS-282 (Reference docs) --- src/docbkx/security.xml | 34 +++++++++++++++++++++++++++++++++- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/src/docbkx/security.xml b/src/docbkx/security.xml index d40527f9..a7d88afb 100644 --- a/src/docbkx/security.xml +++ b/src/docbkx/security.xml @@ -1389,6 +1389,38 @@ DirectReference, Thumbprint, SKIKeyIdentifier or EmbeddedKeyName. + + If the EmbeddedKeyName type is chosen, you need to specify the + secret key to use for the encryption. The alias of the key is set via the + securementEncryptionUser property just as for the other key identifier types. + However, WSS4J requires a callback handler to fetch the secret key. + Thus, securementCallbackHandler must be provided with a + KeyStoreCallbackHandler pointing to the appropriate keystore. + By default, the ds:KeyName element in the resulting WS-Security header takes the + value of the securementEncryptionUser property. To indicate a different name, + set the securementEncryptionEmbeddedKeyName with the desired value. + In the next example, the outgoing message will be encrypted with a key aliased + secretKey whereas myKey will appear in + ds:KeyName element: + + + + + + + + + + + + + + + + + + +]]> The securementEncryptionKeyTransportAlgorithm property defines which algorithm to use to encrypt the generated symmetric key. Supported values are @@ -1435,4 +1467,4 @@ - \ No newline at end of file +