The data will be encrypted in DB therefore a DB Admin won’t be able to steal it.
Two possible implementations:
AddQueueItem add a property
SpecificData works exactly like now and won’t be Encrypted.
SpecificDataEncrypted won’t be visible in the Orchestrator UI and only a robot can have access to it.
Pros: Full Flexibility to decide what data is Encrypted
Cons: Pressure on the developer to decide which goes Encrypted and which not. He will need to work with two QueueItem properties.
2.In the Orchestrator you have the option to encrypt the queue. Encrypted Queue means the entire Specific Data get Encrypted and not available in UI.
Pros: Centralized governance - decide at the Orchestrator level (and not at the process design level) what queue goes encrypted
Cons: Less flexibility. Everything will be encrypted or everything will be visible. Sometimes you need some data for debug, verify.
Note. This feature is dependent on the
@andrzej.kniola @sajal.chakraborty @richarddenton @b_s Please advise