Hi, 1. Would like to encrypt sensitive information in process instan

vikask146 over 9 years ago

Hi,

1. Would like to encrypt sensitive information in process instance. For an example, if I store SSN in one input task then I should be able to store in text data type (encrypt text()) and also should be able to decryption of the same field in next input task if needed.

2. Can we store the same encryption form variable in application database ? If yes then any specific data type to be declared in DB table.

3. AFAIK, process instance data gets store in Process Tables ( Business Data Store). Would like to confirm that how this encryption variable is storing in this database ?

The main intention to stop accessing sensitive information from the system.

Any other inputs will be appreciated.

Discussion posts and replies are publicly visible

0 Myles Weber
Appian Employee
over 9 years ago

I would recommend reviewing the encrypted text component and data type:
forum.appian.com/.../SAIL_Components.html
forum.appian.com/.../Appian_Data_Types.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

1) For this Myles suggestion should work, forum.appian.com/.../SAIL_Components.html

2) PV values are stored in KDBs. Using EncryptedText it will always be encrypted anyway.

3) You can choose and configure what all process instance data be stored in the business data store.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vikask146 over 9 years ago

Thank you both of you but would like to know more about 3rd point. How can we go for selective variables or data points of process instance and then store in KDB files
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Shyam Bommakanti
Certified Lead Developer
over 9 years ago

business datastore <> KDB. All process data gets stored in KDB.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mayankk718 over 9 years ago

As per my knowledge, the following should stand true :-

All Appian process related data is stored in KDB files (in Appian server) automatically. Encrypted data should be treated as normal text and stored in KDB file(s). During retrieval, that excrypted text is retrieved as it is, and if you decrypt it, then internally, that encrypted text is transformed back to its original form, as the "encryption algorithm" is reversed using the same "key" which was used during encryption.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mayankk718 over 9 years ago

Encrypted variable should be treated as normal text (string) internally.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vikask146 over 9 years ago

Encrypted data should be treated as normal text and stored in KDB file(s). -- Are you saying Variable which is encrypted in process will not be stored as encrypted form in KDB ? I would like to confirm that the variable which is encrypted should remain encrypted in KDB also until we use again in another task as decryption
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mayankk718 over 9 years ago

No, I am talking about the data type (text). The value may be stored in encrypted or unencrypted form. For that you would need access to the server.

Also, Between Process Instances and KDB files, there are XMLs. So it goes like ths, "Process instances" --> [Data Transfer] --> "XMLs" --> [Data Transfer] --> KDB Files. If you have on premise server, find the XML of your process instance, look inside it how your variable is stored (encrypted or unencrypted), it would be stored in similar fashion into the KDB files (if I am not wrong).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mayankk718 over 9 years ago

I believe that even KDB files can be queried using Java, but I haven't reached there till now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mayankk718 over 9 years ago

I think that even KDB files can be queried using Java (I am not sure), but I haven't reached there till now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel