> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/9.9/instance-administration/authentication/github.md).
# GitHub
In SonarQube Server 9.9, to allow users to log in with GitHub credentials, you must use a GitHub App.
{% hint style="info" %}
**For AI agents:** You're in the SonarQube Server 9.9 documentation. For a list of all 9.9 pages, see the [SonarQube Server 9.9 page index](https://152261287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBmptmznn7RpPe5u7vdup%2Fuploads%2F7O6jgZAiehDGe0FMXDaC%2Fsonarqube-server-9.9-llms.txt?alt=media). For the whole site, see the [page index](https://docs.sonarsource.com/llms.txt) or the [full text](https://docs.sonarsource.com/llms-full.txt). For another version, replace 9.9 in the URL with that version. The [latest version](https://docs.sonarsource.com/sonarqube-server/) has no version number in its URL.
{% endhint %}
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](https://docs.github.com/en/free-pro-team@latest/developers/apps/creating-an-oauth-app). Specify the following settings in your OAuth App:
* **Homepage URL** – the public URL of your SonarQube Server instance. For example, `https://sonarqube.mycompany.com`. For security reasons, HTTP is not supported, and you must use HTTPS. The public URL is configured in SonarQube Server at **Administration** > **General** > **Server base URL**.
* **Redirect URI** – your instance's base URL. For example, `https://yourinstance.sonarqube.com`.
## Setting your authentication settings in SonarQube Server
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.
4. Enter the allowed organizations in the **Organizations** field.
{% hint style="warning" %}
If the allowed organizations are not entered, any user with a GitHub account can log in to the SonarQube Server instance, even if the GitHub App used for authentication is private.
{% endhint %}
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 Server 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](/sonarqube-server/9.9/instance-administration/authentication/overview.md) for more detail about this feature’s general behavior.
{% hint style="info" %}
When group synchronization is configured, the delegated authentication source becomes the only place to manage group membership, and the user’s groups are re-fetched with each login. It is not possible to use both manual group memberships and group synchronization (via your ALM integration) for the same user.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.sonarsource.com/sonarqube-server/9.9/instance-administration/authentication/github.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.