This version of the SonarQube documentation is no longer maintained. It relates to a version of SonarQube that is not active.

See latest version
Start Free
10.0 | Instance administration | Authentication and provisioning | GitHub

Was this page helpful?


On this page

To allow users to log in with GitHub credentials, you must use a GitHub App. We highly recommend that you set up a dedicated one.

Creating a dedicated app for authentication

If you want to use a dedicated app for GitHub authentication, you can create a GitHub OAuth app. You'll find general instructions for creating a GitHub OAuth App here. Specify the following settings in your OAuth App:

  • Homepage URL – the public URL of your SonarQube server. For example, For security reasons, HTTP is not supported, and you must use HTTPS. The public URL is configured in SonarQube at Administration > General > Server base URL.
  • Authorization callback URL – your instance's base URL. For example,

Setting your authentication settings in SonarQube

Navigate to Administration > Configuration > General Settings > Authentication > GitHub Authentication and update the following:

  1. Enabled – set the switch to true.
  2. Client ID – the client ID is found below the GitHub App ID on your GitHub App's page.
  3. Client Secret – the client secret is found below the client ID on your GitHub App's page.

Now, from the login page, your users can connect their GitHub accounts with the new Log in with GitHub button.

GitHub group synchronization

To associate GitHub Teams with existing SonarQube groups of the same name, enable Synchronize user groups by navigating to Administration > Configuration > General Settings > Authentication > GitHub 

See the Group synchronization section on the Overview page for more details about this feature’s general behavior.

© 2008-2024 SonarSource SA. All rights reserved. SONAR, SONARSOURCE, SONARLINT, SONARQUBE, SONARCLOUD, and CLEAN AS YOU CODE are trademarks of SonarSource SA.

Creative Commons License