GitHub Enterprise Expansion

GitHub Enterprise Integration Overview

This GitHub Enterprise integration builds on the existing GitHub integration within the Rezonate platform, specifically designed to enhance identity security through OIDC-based federation between EntraID and GitHub. The integration detects key federation relationships and tenant-level policies, offering greater control and reducing potential misconfigurations.

Key Features:

1. Federation Detection: Automatically identifies and monitors the federation between EntraID and GitHub via OIDC, improving overall visibility into authentication flows.

2. Policy Detection: Detects tenant-level configurations for additional SAML and OIDC providers, ensuring policy alignment across federated identity systems.

3. MFA Exposure Improvement: By accurately detecting these federations and policies, the integration helps minimize false-positive MFA issues, leading to smoother authentication experiences.

This integration provides enhanced coverage for organizations using GitHub Enterprise, ensuring proper identity configuration and reducing security gaps related to authentication mechanisms.

---

Integrating Steps

This integration Requires READ-ONLY Access and has to be performed by an Enterprise Administrator

1. Log in to GitHub with a GitHub Enterprise admin account

2. On the top-right corner of the screen, click on the user’s avatar

3. Click on “Your enterprise”

4. Copy the and share with Rezonate the GitHub enterprise name from the redirected url: https://github.com/enterprises/<enterprise_name>

5. Create a classic Personal access token:

6. On the top-right corner of the screen, click on the user’s avatar -> Click on “Settings”

   
7. From the left pane menu, scroll to the bottom of the page and click on “Developer settings”

8. From the left pane, expand “Personal access tokens” and choose “Tokens (classic)”

9. Click on “Generate new token” and choose “Generate new token (classic)”

10. Name the token “Rezonate Integration Access Token”, Set the expiration to 1 year.

11. Select the following scopes:

    1. read:org

    2. read:enterprise

    3. read:user

    4. user:email

12. Click “Generate token”.

Share back with Rezonate the following:

• Enterprise Name (As extracted from the URL)

• The generated Token.