Remove OAuth Access Token for all users on an application that is no longer in use
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This article will provide steps to remove an unwanted OAuth Access Token on all of your user profiles to an application that you no longer have access to.
This process should be applied when Confluence no longer has a direct link to the Application, but the application has not removed the link from your users. OAuth Access Token may remain active on Confluence side.
Environment
Confluence Server or Data Center
Solution
Always backup your data before performing any modifications to the database.
This involves a restart of Confluence. Please make sure to perform the steps on a scheduled downtime or off business hours.
Log into your Confluence database and run the following SQL query:
select * from bandana where BANDANAKEY like '%com.atlassian.oauth.serviceprovider.ServiceProviderTokenStore.token%';This query will help us identify the OAuth Access token value on the
bandanavaluecolumn. Take note of this value- Plan a scheduled downtime not to impact your business, or perform the steps during off-hours
- Shutdown Confluence;
Take a backup from your Confluence database in case we may need to revert it to its pre-delete statement state.Execute the below query:
delete from BANDANA where BANDANAKEY like 'com.atlassian.oauth.serviceprovider.ServiceProviderTokenStore.token%' and bandanavalue like '%<VALUE_EXTRACTED_FROM_THE_1ST_STEP>%';Restart the application.
- The external application will be removed from all profiles.