GitHub AE uses SAML SSO for user authentication. You can centrally manage access to GitHub AE from an IdP that supports the SAML 2.0 standard. You'll configure identity and access management for GitHub AE by entering the details for your SAML IdP during initialization. For more information, see "Initializing GitHub AE."
After you configure the application for GitHub AE on your identity provider (IdP), you can provision access to your enterprise by assigning the application to users and groups on your IdP. For more information about SAML SSO for GitHub AE, see "Configuring SAML single sign-on for your enterprise."
By default, your IdP does not communicate with GitHub AE automatically when you assign or unassign the application. GitHub AE creates a user account using SAML Just-in-Time (JIT) provisioning the first time someone navigates to GitHub AE and signs in by authenticating through your IdP. You may need to manually notify users when you grant access to GitHub AE, and you must manually deactivate the user account on GitHub AE during offboarding. You can use SCIM to provision and deprovision user accounts and access for GitHub AE automatically when you assign or unassign the application on your IdP. For more information, see "Configuring user provisioning for your enterprise."
To learn how to configure both authentication and user provisioning for your enterprise with your specific IdP, see "Configuring authentication and provisioning with your identity provider."
The following IdPs are officially supported for integration with GitHub AE.
Note: GitHub AE single sign-on (SSO) support for Okta is currently in beta.
|IdP||SAML||User provisioning||Team mapping|
|Azure Active Directory (Azure AD)|
If you use Okta as your IdP, you can map your Okta groups to teams on GitHub AE. For more information, see "Mapping Okta groups to teams."
- SAML Wiki on the OASIS website
- System for Cross-domain Identity Management: Protocol (RFC 7644) on the IETF website
- Restricting network traffic to your enterprise