OAuth scopes and API endpoints

An overview of which OAuth scopes are requested when authorizing access to your Git Provider

Relevant when using the Individual Access (OAuth 2.0) authentication method.

See Access token scopes and API endpoints when using Managed Access

Git for Confluence uses OAuth to connect to your Git provider. Once you sign in with your Git account your will be asked to give Git for Confluence a few permissions. These permissions are called OAuth scopes, they define what Git for Confluence is allowed to do when you acknowledge the connection.

Have a look at the OAuth scopes that are required for your specific Git provider and see what API endpoints we use for this integration.

Github OAuth scopesGitlab OAuth scopesBitbucket OAuth scopesAzure DevOps OAuth scopes

Withdraw authorization for a Git provider

Withdrawing authorization for a Git provider can be done via the providers. Below are a few examples for where to find more information:

• BitBucket: https://bitbucket.org/account/settings/app-authorizations/

• GitHub: https://github.com/settings/applications

• GitLab: https://gitlab.com/-/profile/applications

• Azure DevOps https://dev.azure.com/YOURUSERNAME/_usersSettings/authorizations