Skip to main content


Follow these steps to add GitHub as a social sign-in provider for your for your project using the Ory Console.

  1. Sign in to Ory Console and select Social Sign-in.

  2. Click the switch next to the GitHub logo to start the configuration.

  3. Copy the Redirect URI and save it for later use.

  4. Create an OAuth2 app in GitHub. Open a new browser tab, go to Developer settings → OAuth Apps and click New OAuth App.


    Currently, the Ory Console allows you to integrate with GitHub through a GitHub OAuth App. If you want to create an integration through a GitHub App, use the Ory CLI.

  5. Paste the Redirect URI copied from Ory into the Authorization Callback URL field in GitHub and fill in other required app details.

  6. Click the Register application button.

  7. Copy the Client ID of the registered application and paste it into the corresponding field in Ory Console.

  8. In GitHub, click Generate a new client secret, copy the generated string, and paste it into the corresponding field in Ory Console.

  9. Click Save Configuration to enable the social sign-in provider.


These steps cover the basic configuration of a social sign-in provider integration. At this point, the user experience is incomplete. To complete the configuration and ensure a smooth and secure user experience, configure the scopes and data mapping as described in the next section.

Additional configuration

When adding a social sign-in provider, you can customize the integration by defining the OAuth scopes Ory requests from the provider and by setting up custom data mappings.


The Scopes section allows you to define the OAuth scopes Ory requests from the sign-in provider. Defining scopes allows you to interact with the provider's APIs on behalf of the user, or to access additional user data, which is exposed as claims for data mapping.

For GitHub, add the user:email scope for a basic setup.

To learn more about the scopes available for GitHub, read the related documentation.

Data mapping

The Data mapping section allows you to map the data returned by the sign-in provider to traits as defined in the identity schema.

To define the mapping, create a Jsonnet code snippet. Read this document to learn more about Jsonnet data mapping.


GitHub doesn't implement OpenID Connect. Because of this limitation, Ory Identities makes a request to GitHub's User API and adds the user data to std.extVar('claims'). Learn what data is available by reading the GitHub Scopes documentation. Not all GitHub scopes are supported. Check the list of supported scopes in the source code.

In this sample Jsonnet snippet, email_primary is mapped to the identity schema's

local claims = {
email_verified: false,
} + std.extVar('claims');
identity: {
traits: {
// Allowing unverified email addresses enables account
// enumeration attacks, especially if the value is used for
// e.g. verification or as a password login identifier.
// Therefore we only return the email if it (a) exists and (b) is marked verified
// by GitHub.
[if 'email' in claims && claims.email_verified then 'email' else null]:,

Don't save secrets such as API keys, credentials, or personal data directly in Jsonnet code snippets. Jsonnet code snippets used for data mapping aren't stored in an encrypted format in Ory Network.


When you add a social sign-in provider, you can encounter common problems such as:

  • Redirect URI mismatch
  • Redirect loops during registration
  • Domain verification issues

To troubleshoot those issues, read Social sign-in troubleshooting.