Bitbucket OAuth scopes
Required OAuth scopes and used endpoints when connecting to Bitbucket.
Last updated
Required OAuth scopes and used endpoints when connecting to Bitbucket.
Last updated
You can find an overview of all available OAuth scopes for Bitbucket here:
https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/
Git for Confluence requests the following scopes:
repositories:read
account:read
These are the endpoints that are being called with an OAuth token.
This endpoint is being used to retrieve the contents of a resource so we can display it on a Confluence page for you. The content is not being saved on the servers of Git for Confluence. This means that every time a file, or folder, is being viewed on a Confluence page, we will have to retrieve its contents using this endpoint.
Sometimes an error can occur when retrieving content from Bitbucket. Bitbucket tells us that the resource can not be found if it does not exist, or if you do not have access to it. Yet we would like to let you know what the actual problem is.
We use this endpoint to check if the repository exists, if that is the case we assume that the resource does not exist and show that to you in the UI.
If we can not find the repository, we assume that you do not have access to the resource that you are trying to share.