Authorizing An App For Single Sign On Github Docs

Leo Migdal

-Nov 18, 2025, 4:43 AM

authorizing an app for single sign on github docs

To use an OAuth app or GitHub App with an organization that uses single sign-on (SSO), you must first set up your SSO sessions and then authorize the application. If your organization or enterprise uses single sign-on (SSO) and you want to access the organization or enterprise's resources through an OAuth app or GitHub App, you must set up an active SSO session... If you do not have an SSO session with an organization's identity provider when you go through the app authentication flow, you will not be able to request or install the application for that... When you sign in to an application (also known as authorizing it), the token that the app receives can be used against any of the organizations where the app is allowed (via installation or... If you want to sign in to an application but do not want the resulting token to have access to a specific SSO-protected organization, you must first sign out of your SSO session with... You can authenticate to GitHub with single sign-on (SSO) and view your active sessions.

There was an error while loading. Please reload this page. You can access an organization that uses single sign-on (SSO) by authenticating through an identity provider (IdP). Single sign-on (SSO) gives organization owners and enterprise owners a way to control and secure access to organization resources like repositories, issues, and pull requests. Organization owners can invite your personal account on GitHub to join their organization that uses SSO, which allows you to contribute to the organization and retain your existing identity and contributions on GitHub. Access to SSO protected internal resources in an enterprise, such as repositories, projects, and packages, requires an SSO session for any organization in the enterprise.

This allows code and work to be shared across organizations in an enterprise without requiring users to join each organization. If you're a member of an enterprise with managed users, you will instead use a new account that is provisioned for you and controlled by your enterprise. For more information, see Types of GitHub accounts. When you attempt to access most resources within an organization that uses SSO, GitHub will redirect you to the organization's SSO identity provider (IdP) to authenticate. After you successfully authenticate with your account on the IdP, the IdP redirects you back to GitHub, where you can access the organization's resources. If you centrally manage your users' identities and applications with an identity provider (IdP), you can configure Security Assertion Markup Language (SAML) single sign-on (SSO) to protect your organization's resources on GitHub.

To use SAML single sign-on, your organization must use GitHub Enterprise Cloud. For more information about how you can try GitHub Enterprise Cloud for free, see Setting up a trial of GitHub Enterprise Cloud. Single sign-on (SSO) gives organization owners and enterprise owners a way to control and secure access to organization resources like repositories, issues, and pull requests. If you configure SAML SSO, members of your organization will continue to sign into their personal accounts on GitHub.com. When a member accesses most resources within your organization, GitHub redirects the member to your IdP to authenticate. After successful authentication, your IdP redirects the member back to GitHub.

For more information, see About authentication with single sign-on. SAML SSO does not replace the normal sign-in process for GitHub. Unless you use Enterprise Managed Users, members will continue to sign into their personal accounts on GitHub.com, and each personal account will be linked to an external identity in your IdP. Communities for your favorite technologies. Explore all Collectives Ask questions, find answers and collaborate at work with Stack Overflow Internal.

Ask questions, find answers and collaborate at work with Stack Overflow Internal. Explore Teams Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. GitHub Apps provide a powerful way to extend GitHub’s functionality and integrate with external services. Unlike personal access tokens or OAuth apps, GitHub Apps act as their own entities with their own permissions, making them more secure and flexible for many applications.

One of the most critical aspects of working with GitHub Apps is understanding token authorization — how to obtain, manage, and use tokens securely. This article provides a comprehensive look at GitHub App token authorization, covering everything from basic concepts to advanced implementation patterns and best practices. GitHub offers several authentication methods for API access: Understanding these differences helps developers choose the right authentication method for their specific use case. GitHub Apps use two primary token types: To integrate GitHub with Single Sign-On (SSO) and various authentication methods, follow these steps:

Navigate to GitHub Settings > Organization > SSO. Choose a SAML SSO provider (e.g., Okta, Azure AD) and configure the necessary attributes and mappings. Enable SSO and configure the necessary mappings for users and groups. Go to GitHub Settings > Security > Two-Factor Authentication. You can authenticate to a GitHub organization with SAML single sign-on (SSO) and view your active sessions. SAML single sign-on is available with GitHub Enterprise Cloud.

For more information, see "GitHub's products." About authentication with SAML single sign-on You can access an organization that uses SAML single sign-on (SSO) by authenticating through an identity provider (IdP). After you authenticate with the IdP successfully from GitHub, you must authorize any personal access token, SSH key, or OAuth App you would like to access the organization's resources. Authorizing an SSH key for use with SAML single sign-on Given that GitHub is the most popular platform for developers to build and ship code, if you are building an application for other developers, you should consider allowing users to log in using their...

This can also give you access to verified user metadata to populate their user profiles. GitHub social login is easy to set up with Auth0. Social login is Single Sign-On (SSO) for end-users. Users can log in to applications or websites using their existing login information from a social network provider like Facebook, Twitter, or GitHub. Social login simplifies registration and login transactions for end-users as they don't need to create a new account specifically for your application or website. Additionally, social login improves the onboarding experience, as you can gather up-to-date user information from the social network provider in the background without creating any friction or compromising user experience.

What if your users modify their GitHub profile information? By default, Auth0 automatically syncs GitHub user profile data with each user login, which ensures that changes made in the user's GitHub profile are automatically updated in Auth0. Optionally, you can disable user profile data synchronization to keep the scope of updating user profile information within your application. Let's get started with using GitHub to log in!

Authorizing An App For Single Sign On Github Docs

People Also Search

To Use An OAuth App Or GitHub App With An

There Was An Error While Loading. Please Reload This Page.

This Allows Code And Work To Be Shared Across Organizations

To Use SAML Single Sign-on, Your Organization Must Use GitHub

For More Information, See About Authentication With Single Sign-on. SAML