See how Ramp uses ConductorOne
ConductorOne

ConductorOne Docs

GitHub connector

Integrations with the applications from which ConductorOne pulls identity data are called connectors.

Overview

GitHub is a very popular development tool and Git repository hosting service. Because GitHub touches the entire software development lifecycle, it often has sensitive data about customers, environments, and infrastructure. ConductorOne connects to your GitHub instance to manage entitlements for access.

Availability

General availability. The GitHub integration is available to all ConductorOne users.

Capabilities

  • Sync identities from GitHub to ConductorOne
  • Entitlements Supported:
    • Groups
    • Projects

Requirements

Connecting to your GitHub environment, you will need:

  • Super Administrator role in ConductorOne
  • Org Owner access in GitHub

Integrate your GitHub instance

ConductorOne uses Personal Access Tokens to manage access.

If you’re using SAML single sign-on, avoid a You must grant your Personal Access token access to this organization error by following the Authorizing a personal access token for use with SAML single sign-on instructions in the GitHub documentation.

Step 1: Create a GitHub Personal Access Token

  1. In GitHub, click your profile photo, then click Settings.

  2. In the left sidebar, select Developer settings.

  3. Click Personal access tokens > Generate new token.

  4. Name your token (for example, ConductorOne Integration). Optionally, add a token expiration date.

  5. Select the following Scopes:

    • repo - select all
    • admin:org - select all if using ConductorOne for GitHub provisioning (see the note below), or read::org otherwise
    • user - select all

    Important: The write::org scope is used by ConductorOne when automatically provisioning and deprovisioning GitHub access on your behalf. If you do not want ConductorOne to perform these tasks for you, do not give your token this scope.

  1. Click Generate token. Copy and save the new token. We’ll use it in Step 3.

If you use SAML SSO, you must authorize the PAT using these instructions.

Step 2: Locate your GitHub organization name

  1. In GitHub, click your profile photo, then click Organizations.

  2. Make a note of your Organization name. We’ll use it in Step 3.

Step 3: Add your GitHub credentials to ConductorOne

  1. In ConductorOne, click Integrations > GitHub.
  2. If this is your first GitHub integration, the integration form opens automatically. Otherwise, click Add Connector.
  3. In the Organization field, enter the name of your GitHub organization.
  4. Paste the token you generated in Step 1 into the Personal Access Token field.
  5. Click Next.
  6. A new GitHub page opens with your saved credentials.

That’s it! Your GitHub instance is now integrated with ConductorOne.