Secure Fields for JIRA
Page tree

Versions Compared

Old Version 11

changes.mady.by.user Inga

Saved on

compared with

New Version 12

changes.mady.by.user Inga

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When storing sensitive data such as passwords or license keys, the main concern is to ensure its proper protection.
Secure Password Custom Field enables you to store private information behind a secure mask and prevent unauthorized access to it.

(Important: Extra authentication enabled)

Permissions

Use a custom field permission scheme to define who can access the field, decrypt, change its value or view the history of the field.
Issues -> Fields -> Custom fields permission schemes

Table of Contents
stylesquare

Expand
titleRead more about View field permission

Users with only View field permission can see the Password field on issue screen.  
The value of the field is shown encrypted and cannot be unmasked or edited by the current user.

Expand
titleRead more about Edit field value permission

If a user with Edit field value permission clicks on (blue star), the Overwrite value button appears. It enables the user to enter new data into the Password field.
The current value will be not shown as the user does not have permission to decrypt the field.

Expand
titleRead more about Decrypt field value permission

After clicking on (blue star), users with Decrypt field value permission (extra authentication disabled) get the next options:

  • Show value - data will be decrypted and the field value is shown:

  • Edit value - data will be decrypted and the field value is available for editing:

  • Copy to clipboard - allows the user to copy the field value to the clipboard.

If extra authentication enabled, the user will be prompted to authorize before attempting any of the actions (show/edit/copy the value).

If authorization fails, none of the options (show/edit/copy the value) are available. A user will get an error message.

History

Tip

Know if and when someone accessed sensitive data.

Every attempt to decrypt, edit, or copy the value of the Password field is recorded in the field's history. Furthermore, unsuccessful attempts are stored as well.