GitHub Application Integration Setup

Getting started

BalkanID recommends creating a separate service account for the purposes of this integration, instead of using personal or employee named accounts.

Requirements

  • Personal Access Token

  • Organization Name

Getting your Configuration

  1. Create a personal access token using the instructions found here.

  2. Ensure that token scopes are according to image given below.

Authorizing a personal access token for use with SAML single sign-on

To use a personal access token (classic) with an organization that uses SAML single sign-on (SSO), you must first authorize the token.

For the personal access token, you'd like to authorize, click Configure SSO. If you don't see Configure SSO, ensure that you have authenticated at least once through your SAML IdP to access resources on GitHub.com. For more information, see "About authentication with SAML single sign-on."

More details here.

Configure GitHub in your BalkanID tenant

  1. Login to the BalkanID application and switch to the tenant you would like to add your integration to.

  2. Head to Integrations > Add Integration, select Github.

  3. Set up the Primary Application owner (mandatory) and the Description, if any. Set up Secondary Application Owner(s), if any.

    Select the Extraction Type. From here, you can configure your application using one of the following methods:

    1. Direct integration - Provide your Github Personal Access Token and Organization obtained above to set up a direct connection with BalkanID.

    2. SCIM integration - Provide SCIM server credentials to set up a SCIM connection with BalkanID.

    3. Manual file upload - Upload Entity and Entity Relations through a .CSV file upload. Contact the team for assistance with this.

    4. Automated upload using API - You can upload data using our Bulk APIs with the help of an API key which will be provided to you. Please refer to the entity and entity relation upload docs for specific instructions on uploading your data through the API.

  4. Click on next to move onto Optional Configuration.

  5. Fill Optional configuration, if required.

  6. Once you filled in the information, click Save. Your integration is now configured and you will see the status of the integration displayed alongside other integrations on the Integrations page. When data is available, the integration Status will read Connected and the integration Message will read Data available.

Integration Scopes

Read Only (Access Review) Scopes
Lifecycle Management Scopes

repo

repo

write:packages -> read:packages

write:packages -> read:packages

admin:org -> read:org

admin:org

admin:public_key -> read:public_key

admin:public_key -> read:public_key

admin:repo_hook -> read:repo_hook

admin:repo_hook -> read:repo_hook

user

user

admin:enterprise -> read:enterprise

admin:enterprise

audit_log

audit_log

project

project

Last updated

Was this helpful?