JIRA Issues Macro: $exceptionMessage displays on page in Confluence
Platform Notice: Data Center Only - This article only applies to Atlassian apps on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
JIRA issues macro is showing error '$exceptionMessage' for some users.
Cause
After moving Confluence from Atlassian Cloud to a Atlassian Server environment, there is a corruption to the OAuth tokens being used in the database.
Resolution
Warning: Backup your database before proceeding.
Before running any SQL in this article, create a full backup of your database. This is a database-level operation with no undo other than a backup restore. Only proceed if you're comfortable running SQL directly against the database, and test on a staging or cloned environment first, wherever possible.
Backup the Confluence database.
Delete the existing application link.
Shutdown Confluence.
Run the following query on the Confluence database:
DELETE FROM BANDANA WHERE BANDANAKEY LIKE '%oauth%';Start Confluence.
Recreate the application link.
Verify that the application link is working properly for users.
Was this helpful?