Jira 9.0 and JSM 5.0 compatibility, plus minor fixes

• Compatibility with Jira 9.0 and Jira Service Management 5.0
• PGP: corrected version tag in PGP encrypted emails
• Jira Service Management: if encryption to a JSM customer fails, a link to the customer profile link is now sent

Jira 9.0 and JSM 5.0 compatibility, plus minor fixes

• Compatibility with Jira 9.0 and Jira Service Management 5.0
• PGP: corrected version tag in PGP encrypted emails
• Jira Service Management: if encryption to a JSM customer fails, a link to the customer profile link is now sent

This release fixes an issue with inbound email processing.

• Jira Service Management: the Jira standard mail handler and a JSM email request handler can now be configured to use the same IMAP mailbox
• Improved compatibility with third-party app inbound email processing

This release fixes an issue with inbound email processing.

• Jira Service Management: the Jira standard mail handler and a JSM email request handler can now be configured to use the same IMAP mailbox
• Improved compatibility with third-party app inbound email processing

New features and many improvements, mostly based on wishes from our customers:

• include link to the original Jira issue in the problem report
• exempt password reset emails from encryption
• replace built-in problem report by custom message contents
• enable support for incoming PGP/inline encrypted emails
• support for some problematic PCKS#12 server key stores
• improved matching and error logging for S/MIME server certificates
• tolerant parsing of line breaks in PGP ASCII keys
• improved PGP signature check
• specific error indicator symbols for incoming emails
• Verify Settings now always also flushes cache to avoid confusion
• updated cryptographic library to BouncyCastle 1.7.0 with several fixes and improvements
• support for display name in server email address

Fixes:

• PGP encryption failure adds proper error indicator symbol to incoming emails
• PGP signature check always finds matching user key

New features and many improvements, mostly based on wishes from our customers:

• include link to the original Jira issue in the problem report
• exempt password reset emails from encryption
• replace built-in problem report by custom message contents
• enable support for incoming PGP/inline encrypted emails
• support for some problematic PCKS#12 server key stores
• improved matching and error logging for S/MIME server certificates
• tolerant parsing of line breaks in PGP ASCII keys
• improved PGP signature check
• specific error indicator symbols for incoming emails
• Verify Settings now always also flushes cache to avoid confusion
• updated cryptographic library to BouncyCastle 1.7.0 with several fixes and improvements
• support for display name in server email address

Fixes:

• PGP encryption failure adds proper error indicator symbol to incoming emails
• PGP signature check always finds matching user key

This release improves S/MIME email signing by updating the hash algorithm to sha-256. It is is recommended for customers who use S/MIME signatures in outgoing emails.

This release improves S/MIME email signing by updating the hash algorithm to sha-256. It is is recommended for customers who use S/MIME signatures in outgoing emails.

This release fixes an issue with new or changed S/MIME certificates not being retrieved from the LDAP user directory

This release fixes an issue with new or changed S/MIME certificates not being retrieved from the LDAP user directory

Changes in this version are:

• fixed an issue with selecting the S/MIME certificate to decrypt with from server key stores containing certificates from different issuers
• fixed an issue with the key validity check complaining about non-obligatory CRL entries
• added a check if any keys/certificates can actually be read when verifying keystore file settings

Changes in this version are:

• fixed an issue with selecting the S/MIME certificate to decrypt with from server key stores containing certificates from different issuers
• fixed an issue with the key validity check complaining about non-obligatory CRL entries
• added a check if any keys/certificates can actually be read when verifying keystore file settings

This release brings new features and improvements:

• full verification of signatures in incoming emails
• add symbols to incoming emails to indicate encryption and signature in Jira (default is off)
• support for additional or external LDAP server
• deferred storage of extracted certificates and keys for newly created users
• sorted order in which keys from different sources are used
• clarified error messages and warnings in key server verification
• log compile timestamp for easier problem analysis

Fixes

• corrected incomplete error message from PGP server

This release brings new features and improvements:

• full verification of signatures in incoming emails
• add symbols to incoming emails to indicate encryption and signature in Jira (default is off)
• support for additional or external LDAP server
• deferred storage of extracted certificates and keys for newly created users
• sorted order in which keys from different sources are used
• clarified error messages and warnings in key server verification
• log compile timestamp for easier problem analysis

Fixes

• corrected incomplete error message from PGP server

Fixed

• Tweak values now display correctly with special characters
• Tweaks now properly reset to their default if deleted

Improved

• Compatibility work-around for SMTP connectors of Jira Email This Issue app
• Decode mail contents before applying skipEncryptionRegex tweak
• PCKS#12 keystores without aliases now work
• Check missing outgoing mail server
• New tweak to optionally create opaque signatures

Fixed

• Tweak values now display correctly with special characters
• Tweaks now properly reset to their default if deleted

Improved

• Compatibility work-around for SMTP connectors of Jira Email This Issue app
• Decode mail contents before applying skipEncryptionRegex tweak
• PCKS#12 keystores without aliases now work
• Check missing outgoing mail server
• New tweak to optionally create opaque signatures

Improvements

• Now determines server key or certificate for decryption under all circumstances
• Improved validation of key servers and key stores

Improvements

• Now determines server key or certificate for decryption under all circumstances
• Improved validation of key servers and key stores

This feature release adds LDAP support for PGP servers

Additional improvements and fixes:

• Accept PGP cipher preferences independent from key trust level
• PGP default cipher is AES128 instead of DES3
• Allow Jira Service Management customers to upload for active encryption types only

This feature release adds LDAP support for PGP servers

Additional improvements and fixes:

• Accept PGP cipher preferences independent from key trust level
• PGP default cipher is AES128 instead of DES3
• Allow Jira Service Management customers to upload for active encryption types only

Fixes

• Jira Service Management (JSD): identify project from customer emails
• Do not sign emails when certificate or key expired
• Reject DES encrypted email for security reasons

New features

• Jira Service Management (JSD): customers can now be enabled to upload their S/MIME certificates or PGP keys
• Mail subject encryption: keep ID in subject to allow for threaded email grouping by mail clients
• Warn if other users use the same email address
• S/MIME: set capabilities in sent emails
• LDAP: full support of authentication, filters, SSL connections

Improvements

• Sophisticated address matching supports recipient address in to, cc, or even bcc header
• Improved project identification
• Improved handling of multiple users having the same email address
• Skip inactive users when searching for address matches
• Improved solutions hints for installation problems
• Protected headers: skip for in unencrypted emails
• Protected headers: compatibility work-around for Outlook 2016

...and many more minor improvements!

Fixes

• Jira Service Management (JSD): identify project from customer emails
• Do not sign emails when certificate or key expired
• Reject DES encrypted email for security reasons

New features

• Jira Service Management (JSD): customers can now be enabled to upload their S/MIME certificates or PGP keys
• Mail subject encryption: keep ID in subject to allow for threaded email grouping by mail clients
• Warn if other users use the same email address
• S/MIME: set capabilities in sent emails
• LDAP: full support of authentication, filters, SSL connections

Improvements

• Sophisticated address matching supports recipient address in to, cc, or even bcc header
• Improved project identification
• Improved handling of multiple users having the same email address
• Skip inactive users when searching for address matches
• Improved solutions hints for installation problems
• Protected headers: skipped for unencrypted emails
• Protected headers: compatibility work-around for Outlook 2016

...and many more minor improvements!

This release fixes an issue with Jira 8.10+ which caused Jira Service Desk email channels not to function properly any more.

This release fixes an issue with Jira 8.10+ which caused Jira Service Desk email channels not to function properly any more.

This release fixes an issue with POP accounts for incoming email.

This release fixes an issue with POP accounts for incoming email.

Fixed in 3.2.1

• Fixes an issue with project encryption settings lost when upgrading the app
• Jira 8.10 compatibility

New in 3.2.0

• Data Center approved version available starting with this release
• Support for elliptic curve PGP keys
• Optional encryption of the email subject
• Automatic decryption of protected subjects in incoming email
• Optional extraction of keys or certificates from incoming email

Improved

• PGP encryption now selects symmetric cipher from key preferences
• Improved error checks for key server URLs
• Improved user group selection in large Jira instances
• Updated underlying BouncyCastle crypto libraries
• Protection against certain XSS attacks

Fixed in 3.2.0

• Advanced settings had missing translation key displayed
• Internal test email could be sent during setup if mailer library was not present yet. These emails will now be deleted from email account when encountered.

DATA CENTER USERS:

Please see https://savignano.atlassian.net/l/c/FnKvjZBz for details about this Data Center release

Fixed in 3.2.1

• Fixes an issue with project encryption settings lost when upgrading the app
• Jira 8.10 compatibility

New in 3.2.0

• Data Center approved version available starting with this release
• Support for elliptic curve PGP keys
• Optional encryption of the email subject
• Automatic decryption of protected subjects in incoming email
• Optional extraction of keys or certificates from incoming email

Improved

• PGP encryption now selects symmetric cipher from key preferences
• Improved error checks for key server URLs
• Improved user group selection in large Jira instances
• Updated underlying BouncyCastle crypto libraries
• Protection against certain XSS attacks

Fixed in 3.2.0

• Advanced settings had missing translation key displayed
• Internal test email could be sent during setup if mailer library was not present yet. These emails will now be deleted from email account when encountered.

DATA CENTER USERS:

Please see https://savignano.atlassian.net/l/c/FnKvjZBz for details about this Data Center release

New features

• Intelligent ambiguity check for multiple project references
• Separate configuration option for non project related emails (other)
• Optional exemption whitelist to exclude recipients from encryption
• Outgoing emails can be additionally encrypted for server address
• S/MIME: include intermediate certificates if available
• S/MIME: support of PKCS#7 format server key bundle
• S/MIME: extract message text for opaque signed message independent from signature handling
• Plus many more enhancements and fixes

For a detailed list of all improvements, please refer to https://savignano.atlassian.net/l/c/rWU8Kexk

DATA CENTER USERS:

We consider undergoing a Data Center approval. Please check out the above link to learn what this would mean to you.

This release fixes an issue with so-called opaque-signed inbound email. An update is recommended for installations using inbound email processing.

Fixed:

• Extract contents from opaque-signed inbound email before removing signature (application/pkcs7-mime with SignedData)
• Typos

This release proudly offers a bunch of new features!

New features

• Inbound decryption: incoming encrypted emails can be decrypted to be processed and become new issues or comments in existing issues
• Per-project encryption: optional separate encryption settings for each Jira project
• Email signatures: outgoing emails can now be signed
• Email anyone: encrypt email for non-users
• German localisation: adapts when Jira is set to German

Improvements

• Support of PGP keyrings as keystores
• Self-checking to verify that S/Notify has not been modified for increased security
• Self-checking to verify that the mailer library version matches the Marketplace plugin
• Improved check and selection of PGP key and S/MIME certificate
• Improved PGP key and S/MIME certificate management in the user profile
• Improved global administration user interface
• Improved information in Get Started and added self-checking to warn of problems
• Some more internal improvements and smaller fixes

• Compatibility update for Jira 8.4
• Improved PGP keyserver compatibility
• Support of verifying PGP keyserver (keys.openpgp.org)

• Added Jira 8.2 compatibility

A few small improvements:

• Verify settings also checks LDAP, if configured
• Display a warning when encryption has been disabled
• Use AES128 algorithm in PGP encryption, as recommend by GnuPG

• Fixes a problem that would prevent the app from being correctly enabled
• Includes fixes for improved email address match for PGP keys

Added LDAP server support

• Allows for automatic retrieval of S/MIME certificates from LDAP
• Automatically uses LDAP servers configured in Jira as user directory
• Extremely simple to configure

This release fixes an issue with S/MIME certificates that have no email field (using only the rfc822name field) not being accepted when uploaded to the user profile.

New

• PGP keyserver urls support hkp and hkps protocols
• Detailed verification tool for global key management settings
• Encryption failure reason now in email report
• Prevent data loss when Jira requires re-login during data entry

Fixes

• Documentation links updated

• Always re-attempt key retrieval after keyserver access failures
• Preserve original Jira email message IDs
• Jira 7.10 compatibility

• Fixes an issue with certain PGP keys where the expiration date wasn't calculated properly.
• Improved the selection of encryption keys, with the most current getting used now.

• Fixes an issue with PGP keys not containing a subpackage

• PGP support added
• Simplified installation through library component
• Added Secure SMTP support
• Major dialog overhaul for better user experience
• Many more enhancements

Compatibility update

• Verified this app is Data Center ready
• Minor fixes

This release comes with

• improved encryption strength
• improved fallback handling for limited Java cryptography support
• additional minor improvements

- Changed the encryption algorithm - Removed file extension limit for certificate upload to improve OS X compatibility- Support MIME version 3 - Improved addon administration link buttons- Minor improvements

This is our initial release. It is well tested and suitable for production use. You can get full support from us, and your feedback is much appreciated.