...
| Info | ||
|---|---|---|
| ||
The passwords are stored in the database in encrypted format and used only internally. They cannot be reproduced by any Jira user or administrator. However, since encryption of passwords alone cannot be considered fully safe, appropriate access control of your database is a prerequisite to achieve adequate protection. |
Decryption Insights
Key or certificate selection
When S/Notify is installed and active, and Jira inbound processing has been configured, decryption of incoming email will always be attempted. Every time an encrypted email is received, S/Notify checks if it has a private PGP key or S/MIME certificate available that can be used to decrypt the email.
If more than one private S/MIME certificate or private PGP key is in the keystore, S/Notify will automatically select the right one, which is the one the email was encrypted for using the corresponding public key.
If the email cannot be decrypted, it is passed on unchanged to Jira's inbound processing. Note that this usually looks like an attachment but no text to Jira, and may therefore be rejected, depending on the setup of the incoming mail handler.
Encrypted subjects
For encrypted emails with hidden (encrypted) subjects, S/Notify automatically recognizes them and restores the original subject field, so the Jira inbound handler can find the appropriate Jira issue.
For S/MIME, so-called opaque signatures will be decoded and the message contents passed on to inbound processing.
Prior to version 3.1, opaque signature decoding required the Remove signatures option to be active.
Related articles
| Filter by label (Content by label) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...