Skip to end of metadata
Go to start of metadata

The encryption method used for attachments and custom fields is:

AES/CBC/PKCS5Padding


Versions prior to 1.6.3

  • For custom fields: AES/CBC/PKCS5Padding
  • For attachments: DesKeySpec
If you need to downgrade Encryption for Jira for any reason, first you have to decrypt all files. Then you can proceed to install the older version.

If the Jira administrator disables the app, attachments will stay encrypted by default. Users will not be able to open an encrypted attachment, instead, they will see the following picture:


To avoid this error, the admin has to decrypt all attachments before disabling the app. In some cases, users might still see the error picture, because the cache has stored this picture and is not requesting it to the server again.

Solution:

To fix this, the user has to clean their cache and refresh the page. This will download the requested resource again from the server.

Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates). You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time.
For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons. For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.
You can renew maintenance after 12 months at 50% of the current purchase price. Learn more here.




  • No labels