9.5 KiB
title, shortTitle, intro, product, redirect_from, versions, type, topics
| title | shortTitle | intro | product | redirect_from | versions | type | topics | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Configuring SAML single sign-on for Enterprise Managed Users | Configure SAML | You can automatically manage access to your enterprise account on {% data variables.product.prodname_dotcom %} by configuring Security Assertion Markup Language (SAML) single sign-on (SSO). | {% data reusables.gated-features.emus %} |
|
|
tutorial |
|
Before following the steps in this article, make sure that your enterprise uses managed users. You can do so by checking whether your enterprise view has the "Users managed by ACCOUNT NAME" header bar at the top of the screen. If you see this, your enterprise uses managed users and you can follow the steps in this article.
If your enterprise uses personal accounts, you must follow a different process to configure SAML single sign-on. See "AUTOTITLE."
About SAML SSO for {% data variables.product.prodname_emus %}
With {% data variables.product.prodname_emus %}, access to your enterprise's resources on {% data variables.location.product_location %} must be authenticated through your identity provider (IdP). Instead of signing in to {% data variables.product.prodname_dotcom %} with a {% data variables.product.prodname_dotcom %} username and password, members of your enterprise will sign in through your IdP.
After you configure SAML SSO, we recommend storing your recovery codes so you can recover access to your enterprise in the event that your IdP is unavailable.
{% data reusables.enterprise_user_management.SAML-to-OIDC-migration-for-EMU %}
Prerequisites
-
Ensure that you understand the integration requirements and level of support for your IdP. For more information, see "AUTOTITLE."
-
Your IdP must adhere to the SAML 2.0 specification. For more information, see the SAML Wiki on the OASIS website.
{% ifversion emu-public-scim-schema %}-{% endif %} To configure your IdP for SAML SSO with {% data variables.product.prodname_emus %}, you must have a tenant and administrative access on your IdP.
Configuring SAML SSO for {% data variables.product.prodname_emus %}
To configure SAML SSO for your {% data variables.enterprise.prodname_emu_enterprise %}, you must configure an application on your IdP, then configure your enterprise on {% data variables.location.product_location %}. After you configure SAML SSO, you can configure user provisioning.
Configuring your IdP
-
{% ifversion emu-public-scim-schema %}If you use a partner IdP, to install the {% data variables.product.prodname_emu_idp_application %} application, click one of the following links.{% else %}To install the {% data variables.product.prodname_emu_idp_application %} application, click the link for your IdP below:{% endif %}
-
Microsoft Entra ID application in Azure Marketplace (Entra ID was previously known as Azure AD)
-
Okta application in Okta's integrations directory
-
PingFederate downloads website
- To download the PingFederate connector, navigate to the Add-ons tab and select {% data variables.product.prodname_dotcom %} EMU Connector 1.0.
-
-
To configure SAML SSO for {% data variables.product.prodname_emus %} on your IdP, read the following documentation. {% ifversion emu-public-scim-schema %}If you don't use a partner IdP, you can use the SAML configuration reference for {% data variables.product.product_name %} to create and configure a generic SAML 2.0 application on your IdP.{% endif %}
- Entra ID on Microsoft Learn
- "AUTOTITLE"
- PingFederate instructions in the PingIdentity documentation {%- ifversion emu-public-scim-schema %}
- "AUTOTITLE" {%- endif %}
-
To test and configure your enterprise, assign yourself or the user that will configure SAML SSO for your enterprise on {% data variables.location.product_location %} to the application you configured for {% data variables.product.prodname_emus %} on your IdP.
Note
In order to test a successful authentication connection upon configuration, at least one user must be assigned to the IdP.
-
To continue configuring your enterprise on {% data variables.location.product_location %}, locate and note the following information from the application you installed on your IdP.
Value Other names Description IdP Sign-On URL Login URL, IdP URL Application's URL on your IdP IdP Identifier URL Issuer IdP's identifier to service providers for SAML authentication Signing certificate, Base64-encoded Public certificate Public certificate that IdP uses to sign authentication requests
Configuring your enterprise
After you configure SAML SSO for {% data variables.product.prodname_emus %} on your IdP, you can configure your enterprise on {% data variables.location.product_location %}.
After the initial configuration of SAML SSO, the only setting you can update on {% data variables.location.product_location %} for your existing SAML configuration is the SAML certificate. If you need to update the sign-on URL or issuer URL, you must first disable SAML SSO, then reconfigure SAML SSO with the new settings. For more information, see "AUTOTITLE."
{% data reusables.emus.sign-in-as-setup-user %}
{% note %}
Note: {% data reusables.enterprise-accounts.emu-password-reset-session %}
{% endnote %} {% data reusables.enterprise-accounts.access-enterprise %} {% data reusables.enterprise-accounts.settings-tab %} {% data reusables.enterprise-accounts.security-tab %}
-
Under "SAML single sign-on", select Require SAML authentication.
-
Under Sign on URL, type the HTTPS endpoint of your IdP for SSO requests that you noted while configuring your IdP.
-
Under Issuer, type your SAML issuer URL that you noted while configuring your IdP, to verify the authenticity of sent messages.
-
Under Public Certificate, paste the certificate that you noted while configuring your IdP, to verify SAML responses. {% data reusables.saml.edit-signature-and-digest-methods %}
-
Before enabling SAML SSO for your enterprise, to ensure that the information you've entered is correct, click Test SAML configuration. {% data reusables.saml.test-must-succeed %}
-
Click Save.
{% note %}
Note: After you require SAML SSO for your enterprise, the setup user will no longer have access to the enterprise but will remain signed in to GitHub. Only {% data variables.enterprise.prodname_managed_users %} provisioned by your IdP will have access to the enterprise.
{% endnote %}
{% data reusables.enterprise-accounts.download-recovery-codes %}
Enabling provisioning
After you enable SAML SSO, enable provisioning. For more information, see "AUTOTITLE."
Enabling guest collaborators
You can use the role of guest collaborator to grant limited access to vendors and contractors in your enterprise. Unlike enterprise members, guest collaborators only have access to internal repositories within organizations where they are a member.
If you use Entra ID or Okta for SAML authentication, you may need to update your IdP application to use guest collaborators. For more information, see "AUTOTITLE."