GitHub
How to integrate GitHub with Apono to manage access to Github code repositories
A code hosting platform for version control and collaboration tool
Overview
- On-Demand Permissions- Managing organizational users’ on demand access permissions to your cloud services or data repositories at granular level.
- Extended SSO- Extend organizational authentication to infrastructure, applications and data repositories where you don’t have SSO.
- Approval Workflows- Creating approval or trigger-based Access Flows allowing organizational user groups to receive the permissions they need.
- Review User Access Permissions- View each organizational users access permissions across the integrated applications and data sources.
Prerequisites
- Connector version 1.3.2 and later
- Admin, Repo and User permissions to GitHub organization
- Make sure users have their company emails linked to their profiles:
- For GitHub Enterprise Cloud: make sure you sync GitHub with your IdP
- For non-Enterprise organizations: the organization's user email must be set on their public GitHub profile
Step By Step Integration
Get API Token from the Github Developer Settings
- Log into your Github account with the Organization dedicated user
- Click on your Profile (icon with your initials)
- On the menu click on -> Settings and choose Developer Settings -> Personal Access Tokens
- Select all the options under
admin:org
,repo
,user
permissions and Copy token - Create a secret using AWS/GCP/K8s with key
token
and paste the copied value as value
Integrate Apono with Github
- Log into Apono
- Go to the Catalog page -> Developer integrations section
- Click on Connect Github
- Specify the integrations details:
Integration name – type the name of the integration
Organization name – type the name of the github organization you are part of
When building an Access Flow you will reference this name
Secret – paste the created cloud secret name
Troubleshooting
- User doesn't have the right privileges - make sure that the user is part of the organization and that the token includes all the required permissions.
- User might not be found -
- For GitHub Enterprise Cloud: make sure you sync GitHub with your IdP
- For non-Enterprise organizations: the organization's user email must be set on their public GitHub profile
Updated about 1 month ago