Application links do not work after upgrading to 8.20.28

Issue Summary

Application links are broken starting on Jira 8.20.28.

This may impact operations performed by end-users on linked Atlassian applications, such as Confluence 7.19.16 (LTS) version.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Install a vanilla instance of Confluence Data Center 7.19.16.
   • Confluence is used just as an example as the impact could be perceived on other linked Atlassian products.
2. Install a vanilla instance of Jira Data Center 8.20.28.
3. Create an application link with impersonation or OAuth between Jira and Confluence.
   • It does not matter which type of the Application link authentication is used.
4. In Confluence Application Links configuration, we will be getting 500 internal error message:
   
5. Search/Create a new Jira issue, an issue filter, a Jira Chart, etc.
   
   

Expected Results

The application link works as expected and the page in Confluence is able to render all Jira Issues Macros.

Actual Results

The application link isn't working and loading the JIM from a Confluence page fails with messages such as below:

• Jira issue doesn't exist or you don't have permission to view it.
• Jira project doesn't exist or you don't have permission to view it.
• The Jira server didn't understand your search query. If you entered JQL, please ensure that it's correctly formed. If you entered an issue key, ensure that it exists and you have permission to view it.

Notes

• 8.20.28 is running Atlassian OAuth Consumer Plugin v4.0.8 (does not work).
• 8.20.26 is running Atlassian OAuth Consumer Plugin v4.0.3 (works).

Downgrading the version to 4.0.3 in 8.20.28 and the application links from Confluence to Jira is start working.

A similar issue was reported from the bug in 9.9.0 - https://jira.atlassian.com/browse/JRASERVER-75911

Workaround

Option 1

As per the End of life policy, the 8.20.x LTS versions will be EOD by date: 31 Jan 2024, so please consider upgrading Jira to the latest 9.4 LTS version.

Option 2

Take a backup of the following files in the Jira 8.20.28 installation (all nodes) and remove them from their current directory.

<jira-install>/atlassian-jira/WEB-INF/lib/atlassian-oauth-api-4.0.8.jar
<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-oauth-admin-plugin-4.0.8.jar
<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-oauth-service-provider-plugin-4.0.8.jar
<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-oauth-consumer-spi-4.0.8.jar
<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-oauth-service-provider-spi-4.0.8.jar
<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-oauth-consumer-plugin-4.0.8.jar

2. Download the OAuth zip file from the link below:

• oauth-folder.zip

3. Unzip the file. Copy the atlassian-oauth-api-4.0.3.jar from the folder and move it to this path:

<jira-install>/atlassian-jira/WEB-INF/lib/

4. Copy the following jar files:

atlassian-oauth-admin-plugin-4.0.3.jar
atlassian-oauth-service-provider-plugin-4.0.3.jar
atlassian-oauth-consumer-spi-4.0.3.jar
atlassian-oauth-service-provider-spi-4.0.3.jar
atlassian-oauth-consumer-plugin-4.0.3.jar

5. Move them to this path (note that it's different from the one before):

<jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins/

6. Clear plugins cache as detailed in How to clear Jira's plugin cache.
7. Restart all the Jira nodes.