from Jira Support AI:
To resolve the issue where Jira links in Confluence display as placeholders or URLs after upgrading to OAuth 2.0, you must revert the authentication method to OAuth 1.0 with Impersonation.
Root Cause
In Jira Software Data Center (versions 10.x/11.x), OAuth 2.0 currently utilizes a 2-Legged OAuth (2LO) flow. This flow does not pass the individual user's context (impersonation) to the remote application, causing Jira-related macros and gadgets to fail to render data or display errors 1.
Resolution Steps
To restore full macro functionality, follow these steps to reconfigure the link using OAuth 1.0:
1. Remove the OAuth 2.0 Configuration
In Jira: Navigate to Administration > Applications > Application Links. Edit the link to Confluence and remove both Outgoing and Incoming OAuth 2.0 configurations 1.
In Confluence: Navigate to Administration > General Configuration > Application Links and remove the corresponding OAuth 2.0 settings for Jira 1.
2. Configure OAuth 1.0 with Impersonation
In either application, select Create link (or edit the existing one).
Enter the URL of the remote application and select OAuth 1.0 as the authentication provider 2.
Crucial: Ensure that Allow-Impersonation is enabled. This allows the applications to communicate on behalf of the logged-in user 2.
Complete the reciprocal configuration on the second application to ensure the link is healthy in both directions 2.
3. Verify and Re-authenticate
Navigate to a Confluence page with a Jira macro and refresh it.
If prompted, click Authenticate to generate the initial handshake for your user profile 2.
Note: OAuth 1.0 remains a fully supported method for Jira Software and Confluence Data Center integrations until at least March 2029
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.