Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.1.5, 6.4, 6.4.7, 6.4.11, 8.13.2
-
6.01
-
14
-
Severity 3 - Minor
-
1
-
Description
Summary
OAuth token is referring to the old URL after recreating the Application Link between JIRA and Confluence
Environment
JIRA 6.1.5
Confluence 5.7
Steps to Reproduce
- Configure Application Link directly between JIRA and Confluence
- Link Confluence page into JIRA issue and put this JIRA issue key into the linked page
- Authenticate the link to trigger token creation between JIRA and Confluence
- Stop Confluence
- Setup Confluence over SSL
- Start Confluence
- Remove Application Link in both JIRA and Confluence
- Re-create Application Link to run through the SSL connector
- OAuth token has been removed. So, attempt to generate a new token by authenticating the link from JIRA issue and from the Confluence page
This can also be reproduced without configuring SSL, by changing the Base URL for example.
Expected Results
OAuth token in JIRA is referring to the new URL, over HTTPS (SSL)
Actual Results
OAuth token in JIRA is referring to the old URL, HTTP
Notes
Token from the Confluence side is generated correctly.
Workaround
- Follow the steps to remove the Application Links directly from the database in both JIRA and Confluence:
- How to remove Application link directly through JIRA database
- See resolution section on Application Link configuration cannot be deleted via the UI and appears as System Link for Confluence
Attachments
Issue Links
- is related to
-
CONFSERVER-39916 OAuth token is referring to the old URL in Confluence
- Closed
-
BAM-15329 OAuth access tokens pointed at wrong application URL
- Gathering Impact
- was cloned as
-
APL-1272 Loading...