--- title: "Configure OpenID Connect with GitHub" slug: "github" updated: 2026-07-24T09:19:55Z published: 2026-07-24T09:19:55Z canonical: "docs.discngine.com/github" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.discngine.com/llms.txt > Use this file to discover all available pages before exploring further. # Configure OpenID Connect with GitHub ## Overview This guide will walk you through configuring OpenID Connect authentication with GitHub for Discngine Admin Center. Once completed, users will be able to log in using their GitHub credentials. > **Important:** GitHub users must have a public email address configured, as sign-in matches users on their email address. ## Prerequisites Before configuring GitHub OpenID Connect, ensure you have: - Organisation Administrator access to Discngine Admin Center - A [GitHub account](https://github.com/) - Permissions to create OAuth applications on GitHub ## Register a GitHub OAuth Application ### Step 1: Access GitHub Settings 1. Log in to [GitHub](https://github.com/) 2. Navigate to **Settings** (click your profile picture → Settings) 3. In the left sidebar, navigate to **Developer settings** → **OAuth Apps** 4. Click **Register a new application** ![Register a new GitHub OAuth Application](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/github-register-application.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=15JwSnYPY86tNi9Baw649wUYqxpOmVFcRNuccSWqdgE%3D) ### Step 2: Configure OAuth Application Fill in the following fields: 1. **Application name:** Enter a name (e.g., "Discngine Admin Center") 2. **Homepage URL:** Enter your organisation's homepage (e.g., `https://www.yourcompany.com`) 3. **Application description:** (Optional) Add a description 4. **Authorization callback URL:** Set to: `https://account.discngine.cloud/oauth2/callback` 5. Click **Register application** ![GitHub OAuth App Configuration](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/github-app-config.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=3YYibPLRkfyPkq36QcmKStxiPEoKLQNPVlUAYGsfxUM%3D) ### Step 3: Generate Client Secret 1. Once the application is created, you'll see the **Client ID** - copy and save it 2. Click **Generate a new client secret** 3. Copy the **Client Secret** immediately - you won't be able to see it again ![GitHub Client ID and Secret](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/github-client-id-secret.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=NMrSfsbg%2BkyZPQxuPRso5kjUHwbDhtkcAVbhZjH7OHc%3D) ## Configure OpenID Connect in Discngine Admin Center ### Step 1: Access Identity Providers 1. Log in to Discngine Admin Center as an Organisation Administrator. 2. Navigate to **Identity Providers** in the left sidebar or via the **Identity Providers** card on the home page. 3. Click **New Provider** and set **Provider Type** to **OpenID Connect with Issuer URL**. ![Create a new OpenID integration](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/new_idp_provider.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=AWk7wAG8S4dBHVFRHkNigOvMoHqwwtKZhYMbuG6ftG0%3D) ### Step 2: Configure Provider Settings The OpenID Connect form is simplified — you only need the following fields: - **Name:** `GitHub` - **Issuer URL:** `https://github.com` (endpoint discovery happens automatically from this URL) - **Client ID:** the Client ID from GitHub - **Client Secret:** the Client Secret from GitHub Click **Save**. ![GitHub Identity Provider Configuration](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/github-idp-config.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=e1Iq4EaVNrZGbkw2bryleNPnjRp11rUAaPV%2FXUgYZ20%3D) > **Note:** GitHub users must have a public email address configured for sign-in to work. See [GitHub Email Privacy](/public/docs/github#github-email-privacy) below. ### Step 3: Enable for Applications By default, the new provider is not enabled for any application. 1. Open the provider from the Identity Providers page and switch to the **Application Registration** tab. 2. Your applications are listed grouped by environment. Turn the **Enabled** toggle on for each application that should use this provider. 3. Click **Save**. For more details on assigning providers to applications, see [How to Manage Identity Providers](/public/docs/how-to-manage-identity-providers). ## Testing the Configuration ### Step 1: Access Login Page Navigate to `https://admin-<organisation-name>.discngine.cloud/` ### Step 2: Test Login 1. Enter your email address 2. You should see the **Login with GitHub** button 3. Click the button 4. You will be redirected to GitHub's authorization page 5. Review the permissions being requested 6. Click **Authorize** to grant access 7. After successful authentication, you'll be redirected back to Discngine Admin Center ![Login with GitHub](https://cdn.document360.io/dde9293e-c107-4b3e-9774-9c9c296ed970/Images/Documentation/github-login-button.png?sv=2026-02-06&spr=https&st=2026-11-16T05%3A43%3A17Z&se=2026-11-16T06%3A43%3A17Z&sr=b&sp=r&sig=wxoZsCG%2FDzQWuE4Gv8qNMdnVww2yio07DcNEhZYsnDA%3D) ## Troubleshooting ### Common Issues **Email Address Not Available Error** If you see: `An email address was not provided for the user. This account cannot be used to login, unable to complete this login request.` **Solution:** Require users to make their email address public on GitHub - Go to GitHub → Settings → Profile → Public email - Select an email address from the dropdown **Redirect URI Mismatch** - Ensure the callback URL in GitHub exactly matches: `https://account.discngine.cloud/oauth2/callback` - Check for typos and ensure there are no trailing slashes **Invalid Client Credentials** - Double-check that you copied the Client ID and Client Secret correctly - If the secret was lost, generate a new one in GitHub **Scope Issues** - Verify that `user:email` scope is configured - Without this scope, email information won't be available **Authorization Declined** - Users must click "Authorize" when prompted by GitHub - If authorization is declined, they cannot complete the login ## GitHub Email Privacy GitHub allows users to keep their email addresses private. Sign-in via GitHub matches users on their email address, so a **public email address is required** for the account to be recognised in Discngine Admin Center. Ask your users to make their email address public (GitHub → Settings → Profile → Public email) based on your organisation's requirements and your users' privacy preferences. ## Additional Resources - [GitHub - Creating an OAuth App](https://docs.github.com/en/developers/apps/building-oauth-apps/creating-an-oauth-app) - [GitHub OAuth Documentation](https://docs.github.com/en/developers/apps/building-oauth-apps/authorizing-oauth-apps) - [GitHub API Documentation](https://docs.github.com/en/rest) ## Next Steps - [← Back to How to Manage Identity Providers](/public/docs/how-to-manage-identity-providers)