-
Bug
-
Resolution: Tracked Elsewhere
-
Low
-
None
-
5.8
-
1
-
Summary
OAuth token is referring to the old URL after recreating the Application Link between Confluence and another Atlassian application(eg. JIRA)
Environment
JIRA 6.4
Confluence 5.8
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
- Change Base URL in both JIRA and Confluence(example could be switching from FQDN to localhost)
- Remove Application Link in both JIRA and Confluence
- Re-create Application Link
- Revoke any tokens and generate a new OAuth token by authenticating the link from JIRA issue and from a Confluence page
Expected Results
OAuth token in JIRA is referring to the new URL and application name
Actual Results
OAuth token in JIRA is referring to the old URL
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
- relates to
-
JRASERVER-44165 OAuth token is referring to the old URL in JIRA
-
- Gathering Impact
-
-
APL-1272 Loading...