Handler - Encryption
Allows attributes to be saved in an encrypted form
Handler - Encryption
Allows attributes to be saved in an encrypted form
Encryption handler allows attributes to be saved in an encrypted form. Algorithm used for two-way encryption is 3DES and for one-way SHA-512. Encryption key for two-way encryption should be configured in the framework.properties parameter encryptionhandler.key. The one-way encryption does not need an encryption key.
Encryption handler does not currently support multivalue data.
If you add Encryption handler to a template that already has existing data cards, you need to manually save those cards to encrypt the existing values.
Table 1. Optional Attribute Metadata
| Name | Value | Description |
|---|---|---|
Password |
[true | false] |
If the Password value is set to true, the edit mode will print asterisks instead of given value. This setting is suitable for situations where the attribute value is meant to be used by another handler. |
One-way encryption |
[true | false] |
If the One-way encryption value is set to true, the attribute is encrypted with a one-way algorithm (hashing). Also the edit and view mode will print asterisks instead of given value. Default is false, this means two-way encryption is used. This setting is suitable for situations where it is not necessary to get the actual value of the attribute again in a plain text format (e.g., for password fields). |
Algorithm |
[3des | aes256] |
If the Algorithm value is set to 3des, the attribute is encrypted with 3des algorithm. If the Algorithm value is set to aes256, the attribute is encrypted with aes256 algorithm. Default value is 3des. If this algorithm value is changed, the operation of "Generate new data encryption key" has to be performed. This setting is suitable for situations where attribute values need to be encrypted. |
Table of Contents