If you want to create a central encryptioncustom field with a centrally encrypted password, select Password with Central Encryption, enter a name it as you wish and associate it to the a screen. This is useful if the following requirements are to be met:
Any user you You want users to get a password or other data from a password field by entering some their user credentials (password to log-in to Jira)
The user doesn’t want to enter any decryption or a specific encryption key
The password should be stored encrypted in the database
Users should not know the encryption /decryption key but the keys can should be stored on at any path in the network reachable for location Jira can connect to
As soon as the user creates a new password it is automatically encrypted with the given private key
As soon as the user enters user credentials to view a password it is automatically decrypted with the given public key
...
There is only one private/public key pair at a network location (or two different locations).
The private/public key pair is not related to user passwords in any way.
The user needs to enter his user credentials just to access the field. The encryption decryption happens in background.
Users don’t need their own keys.
How to add the custom field
...
Then adjust the configuration of the field and edit the Central Encryption:
...
In the configuration, the admin needs to define a folder paths path to the encryption private key (just text fields, no upload input). This should , which has to be a private key file. Furthermore, the adminneeds to define a folder paths path to the decryption public key. This should has to be a public key file. Both should be uploaded to custom field setting. Jira must be able to search for access this pathlocation. Local and remote paths are possible.
...