Skip to main content

Migrating from SAML to OIDC

If you're using SAML to authenticate members in your empresa con usuarios administrados, you can migrate to OpenID Connect (OIDC) and benefit from support for your IdP's Conditional Access Policy.

Para administrar a los usuarios de tu empresa con tu proveedor de identidad, esta debe habilitarse para Usuarios Administrados de Enterprise, los cuales están disponibles con Nube de GitHub Enterprise. Para obtener más información, consulta la sección "Acerca de Usuarios Administrados de Enterprise".

Note: OpenID Connect (OIDC) and Conditional Access Policy (CAP) support for Usuarios Administrados de Enterprise is in public beta and only available for Azure AD.

About migrating your empresa con usuarios administrados from SAML to OIDC

If your empresa con usuarios administrados uses SAML SSO to authenticate with Azure Active Directory (Azure AD), you can migrate to OIDC. When your enterprise uses OIDC SSO, GitHub will automatically use your IdP's conditional access policy (CAP) IP conditions to validate user interactions with GitHub, when members change IP addresses, and each time a personal access token or SSH key is used.

When you migrate from SAML to OIDC, cuentas de usuarios adminsitrados and groups that were previously provisioned for SAML but are not provisioned by the Usuario Administrado de GitHub Enterprise (OIDC) application will have "(SAML)" appended to their display names.

If you're new to Usuarios Administrados de Enterprise and haven't yet configured authentication for your enterprise, you do not need to migrate and can set up OIDC single sign-on immediately. For more information, see "Configuring OIDC for Enterprise Managed Users."

Migrating your enterprise

Note: To sign in as the setup user, you will need a recovery code. If you do not already have your recovery codes, you can access the codes while signed in as an enterprise owner. For more information, see "Downloading your enterprise account's single sign-on recovery codes."

  1. Before you begin the migration, sign in to Azure and disable provisioning in the existing Usuario Administrado de GitHub Enterprise application.

  2. Sign into GitHub.com as the setup user for your enterprise with the username @SHORT-CODE_admin.

  3. When prompted to continue to your identity provider, click Use a recovery code and sign in using one of your enterprise's recovery codes.

  4. En la esquina superior derecha de GitHub.com, da clic en tu foto de perfil y luego en Tus empresas. "Tus empresas" en el menú desplegable de la foto de perfil en GitHub Enterprise Cloud

  5. En la lista de empresas, da clic en aquella que quieras ver. Nombre de una empresa en la lista de tus empresas

  6. En la barra lateral de la cuenta de empresa, haz clic en Settings (Configuraciones). Pestaña Settings (Configuraciones) en la barra lateral de la cuenta de empresa

  7. En la barra lateral izquierda, haz clic en Security (Seguridad). Security tab in the enterprise account settings sidebar

  8. At the bottom of the page, next to "Migrate to OpenID Connect single sign-on", click Configure with Azure.

    Warning: The migration can take up to an hour, and it is important that no users are provisioned during the migration. You can confirm if the migration is still in progress by returning to your enterprise's security settings page; if "Require SAML authentication" is still checked, the migration is still in progress.

    Screenshot showing the "Configure with Azure" button

  9. Read both warnings and click to continue.

  10. When redirected, sign in to your identity provider, then follow the instructions to give consent and install the Usuario Administrado de GitHub Enterprise (OIDC) application.

    Warning: You must sign in to Azure AD as a user with global admin rights in order to consent to the installation of the Usuario Administrado de GitHub Enterprise (OIDC) application.

  11. In a new tab or window, while signed in as the setup user on GitHub.com, create a personal access token with the admin:enterprise scope and no expiration and copy it to your clipboard. For more information about creating a new token, see "Creating a personal access token."

  12. In the settings for the Usuario Administrado de GitHub Enterprise (OIDC) application in Azure Portal, under "Tenant URL", type https://api.github.com/scim/v2/enterprises/YOUR_ENTERPRISE, replacing YOUR_ENTERPRISE with the name of your enterprise account.

    For example, if your enterprise account's URL is https://github.com/enterprises/octo-corp, the name of the enterprise account is octo-corp.

  13. Under "Secret token", paste the personal access token with the admin:enterprise scope that you created earlier.

  14. To test the configuration, click Test Connection.

  15. To save your changes, at the top of the form, click Save.

  16. In Azure Portal, copy the users and groups from the old Usuario Administrado de GitHub Enterprise application to the new Usuario Administrado de GitHub Enterprise (OIDC) application.

  17. Test your configuration by provisioning a single new user.

  18. If your test is successful, start provisioning for all users by clicking Start provisioning.