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
Ok, the default Snap Execution of Execute Only explains why you weren’t getting any output when validating. Actually, I don’t think the JSON.stringify($entity) is really necessary, since $entity in this context will implicitly convert the input data to a JSON string.
It looks like the web service you’re invoking needs some authentication, and there are different ways of handling that. Please check the docs for the target web service regarding the required authentication.
Did you configure your REST snap with an error view? If so, see if the error_entity field in the error document tells you anything useful.
@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?
