The XMLSecurity DataFormat facilitates encryption and decryption of XML payloads at the Document, Element and Element Content levels (including simultaneous multi-node encryption/decryption using XPATH).
The encrytion capability is based on formats supported using the Apache XML Security (Santaurio) project. Encryption/Decryption is "currently" supported using Triple-DES and AES (128, 192 and 256) encryption formats. Additional formats can be easily added later as needed. (Note: The support currently offered is for symmetric encryption. This means the same keyset is needed at both ends of the communication to encrypt/decrypt payloads).
The capability allows Camel users to encrypt/decrypt payloads while being dispatched or received along a route.
The XPATH reference to the XML Element selected for encryption/decryption.
If no tag is specified, the entire payload is encrypted/decrypted.
A boolean value to specify whether the XML Element is to be encrypted or the contents of the XML Element.
- false --> Element Level
- true --> Element Content Level
A byte array that is used as passPhrase to encrypt/decrypt content. The passPhrase has to be
If no passPhrase is specified, a default passPhrase is utilized. The passPhrase needs to be put together in conjunction
with the appropriate encryption algorithm
- TRIPLEDES (example: "Only another 24 Byte key".getBytes()
The cipher algorithm to be used for encryption/decryption.
The available choices are.
If xmlCipherAlgorithm is not explicitly specified the cipher algorithm employed is XMLCipher.TRIPLEDES
In order to encrypt the payload, the marshal processor needs to be applied on the route followed by the encryptXML() tag.
In order to decrypt the payload, the unmarshal processor needs to be applied on the route followed by the encryptXML() tag.
Given below are several examples of how marshalling could be performaed at the Document, Element and Content levels.