Not often but sometimes, there is a need to encrypt and decrypt messages flowing through IBM Integration Bus and there are some working solutions available in the market to achieve the same.
Since these algorithms are not available by default in ESQL, the next immediate solution is Java. So, if you are comfortable with Java Compute Node and know how to pick the Key from multiple locations like the below , then it is scalable and works like the same way as built-in nodes
- User Defined Property
- Any other valid location in the Message Assembly
Here is a solution which uses AES algorithm to encrypt and decrypt the messages. All you need is 16bytes KEY.
The KEY can be hard coded or its location can be $LocalEnvironment/Destination/Encrypt/Key or any other path which can be defined here
Now, this makes flexible that the KEY can be inside the incoming message or from LocalEnvironment or from Environment tree too.
Let us see how the encrypted message looks like after passing a simple XML file like below
If you are looking for the same solution or would like to know our capabilities in IIB, please contact us at firstname.lastname@example.org/WhatsApp +1 6123058684.
We’ve rich experience in IIB and executed multiple projects since 2013. So, we assure that you get your solution on time in low cost without compromising on quality and efficiency.
2 thoughts on “Cryptography in IIB”
How to configure Encryption node path for public key from compute node
I am using IBM Appconnect enterprise 126.96.36.199
You can set it in LocalEnvironment or any path. This node understand the path and picks the value from there automatically.