Transpose Table data to XML format
Input data(4 rows):
Employee ID Type EmployeeID Address ID Address
Employee_ID A001 1 test1
Employee_ID A001 2 te...
Forum Discussion
Thank you very much for your response Anil. I have modified your pipeline to my problem and attached.
You can see the change in sequence in the Record2 after the join. I need to re-sequence it back to how it was in the right JSON generator. How can I do that?sequence of the data_2018_12_18 (1).slp (7.9 KB)
Thanks and regards,
Sri
@pavan Once encrypted, do I need to pass all the information onward? Is it a security risk to do so?
ENC { "transformation":"AES/CBC/PKCS5Padding", "iv":"[MYIV]", "type":"STRING", "ciphertext":"[MYCIPHERTEXT==]", "key_params": { "passphrase": { "key_gen_iterations":10000, "key_gen_algorithm":"[ALGORITHM]", "key_algorithm":"AES", "key_salt":"[SALTKEY]", "key_size":128 } } }:ENCYes, the information is needed to correctly decrypt the ciphertext.
No, it’s okay to send the IV in the clear and the rest of the information is used to configure the decryption process.
@tstack I have a similar scenario. Please read through the steps.
- We are using Encryption & Decryption in 2 seperate ultra pipelines, where first pipeline would encrypt the password field and send this data to second pipeline & the second pipeline would decrypt the data and use it.
- The problem is we are giving away key information like Type Of Algorithm, IV, Key_SALT over the internet along with the Ciphertext which is a security concern.
- Our design has to have 2 seperate ultra pipelines & not pipeline execute as its an architectural decision.
How can we achieve decrypting the field, without giving away these key attributes?
