Cofnigurar SCIM y el inicio de sesión único de SAML con Okta

About SAML and SCIM with Okta

You can control access to your organization on GitHub and other web applications from one central interface by configuring the organization to use SAML SSO and SCIM with Okta, an Identity Provider (IdP).

SAML SSO controls and secures access to organization resources like repositories, issues, and pull requests. SCIM automatically adds, manages, and removes members' access to your organization on GitHub when you make changes in Okta. For more information, see "About identity and access management with SAML single sign-on" and "About SCIM for organizations."

After you enable SCIM, the following provisioning features are available for any users that you assign your GitHub Enterprise Cloud application to in Okta.

Feature	Description
Push New Users	When you create a new user in Okta, the user will receive an email to join your organization on GitHub.
Push User Deactivation	When you deactivate a user in Okta, Okta will remove the user from your organization on GitHub.
Push Profile Updates	When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on GitHub.
Reactivate Users	When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on GitHub.

Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "Configuring SAML single sign-on for your enterprise using Okta" and "Configuring SCIM provisioning with Okta."

Configuring SAML in Okta

1. In the Okta Dashboard, expand the Applications menu, then click Applications.
2. Click Browse App Catalog.
3. Search for the application named "GitHub Enterprise Cloud - Organization."
4. Click Add Integration.
5. Fill out the form, providing the name of your organization on GitHub and a unique name in the "Application Label" field.
6. Assign the application to your user in Okta. For more information, see Assign applications to users in the Okta documentation.
7. Under the name of the application, click Sign on.
8. Under "SIGN ON METHODS", click View Setup Instructions.
9. Enable and test SAML SSO on GitHub using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "Enabling and testing SAML single sign-on for your organization."

Configuring access provisioning with SCIM in Okta

To use SCIM with your organization, you must use a third-party-owned OAuth app. The OAuth app must be authorized by, and subsequently acts on behalf of, a specific GitHub user. If the user who last authorized this OAuth app leaves or is removed from the organization, SCIM will stop working. To avoid this issue, we recommend creating a dedicated user account to configure SCIM. This user account must be an organization owner and will consume a license.

1. Sign into GitHub using an account that is an organization owner and is ideally used only for SCIM configuration.

2. To create an active SAML session for your organization, navigate to https://github.com/orgs/ORGANIZATION-NAME/sso. For more information, see "About authentication with SAML single sign-on."

3. Navigate to Okta.

4. In the left sidebar, use the Applications dropdown and click Applications.

5. In the list of applications, click the label for the application you created for the organization that uses GitHub Enterprise Cloud.

6. Under the name of the application, click Provisioning.

7. Click Configure API Integration.

8. Select Enable API integration.

   Note

   "Import Groups" is not supported by GitHub. Selecting or deselecting the checkbox has no impact on your configuration.

9. Click Authenticate with GitHub Enterprise Cloud - Organization.

10. To the right of your organization's name, click Grant.

    Note

    If you cannot see your organization, this may be because OAuth app access restrictions are enabled for the organization. To continue, you will need to approve the "OKTA SCIM Integration" app for the organization. For more information, see "Approving OAuth apps for your organization."

11. Click Authorize OktaOAN.

12. Click Save.

13. To avoid syncing errors and confirm that your users have SAML enabled and SCIM linked identities, we recommend you audit your organization's users. For more information, see "Troubleshooting identity and access management for your organization."

14. To the right of "Provisioning to App", click Edit.

15. To the right of "Create Users," select Enable.

16. To the right of "Update User Attributes," select Enable.

17. To the right of "Deactivate Users," select Enable.

18. Click Save.

Further reading

• "Configuring SAML single sign-on for your enterprise using Okta"
• Understanding SAML in the Okta documentation
• Understanding SCIM in the Okta documentation