Summary

Stash User Authorized application (OAuth token) page showing old JIRA URL

• Stash is now known as Bitbucket Server

Steps to Reproduce

1. Setup JIRA with the URL http://jira.domain1
2. Create OAuth Application Link between JIRA and Stash
3. Allow JIRA user to access Stash data
4. Check Stash user "Authorized applications" page http://stash.domain:7990/plugins/servlet/oauth/users/access-tokens
   It is showing Stash server allow JIRA server on jira.domain1 to access Stash data
5. Revoke the access
6. Delete the Application Link
7. Change JIRA server Base URL to http://jira.domain2
8. Access JIRA server with the URL http://jira.domain2
9. Create OAuth Application Link between JIRA and Stash again
10. Allow JIRA user to access Stash data
11. Check Stash user "Authorized applications" page http://stash.domain:7990/plugins/servlet/oauth/users/access-tokens
    It is still showing Stash server allow JIRA server on jira.domain1 (instead of the new baseURL jira.domain2) to access Stash data

Expected Results

Stash User Authorized application (OAuth token) page should be using the new JIRA URL as shown in the Application Links

Actual Results

Still using the old JIRA URL

Notes

Found out that Stash is getting this OAuth Consumer Description from JIRA server database table "oauthconsumer".
Anyway, the Application Link still works fine even though the URL in the description is incorrect

Workaround

1. Backup JIRA database for rollback purposes
2. Shutdown JIRA
3. Edit the table "oauthconsumer" to change the URL and optionally, the name:

   UPDATE oauthconsumer SET consumername='<JIRA_new_name>' WHERE consumername='<JIRA_old_name>'
   UPDATE oauthconsumer SET description='Atlassian JIRA at <new_URL>' WHERE description='Atlassian JIRA at <old_URL>'
   

1. Restart JIRA
2. Delete both Application Links in Stash and JIRA
3. Recreate the Application Links