Integrate a new GitHub Enterprise source
GitGuardian integrates natively with GitHub Enterprise via a GitHub App that you can install on your personal GitHub Enterprise repositories and the repositories of your GitHub Enterprise organizations.
By default, the GitGuardian GitHub app has only read access to your code.
Optionally, it is possible to grant GitGuardian write access to benefit from specific business features (more detail in this dedicated section).
You will need Owner or Manager rights in GitGuardian to set up an integration or customize your settings.
The pre-existing GitGuardian GitHub App cannot be leveraged to integrate with self hosted GitHub Enterprise.
Instead, you will need to create a separate GitHub App on your own GitHub Enterprise instance. This process is extremely
straightforward since GitGuardian will automatically indicate the required configurations to your GitHub Enterprise.
You can refer to the GitHub documentation for more information on GitHub apps.
GitGuardian supports all GitHub Enterprise versions supported by GitHub itself.
Setup your GitHub Enterprise integration
- Navigate to Settings > Workspace > Integrations.
- Click on Configure for GitHub Enterprise.
- Enter the URL of your GitHub Enterprise instance to create your dedicated GitHub app
- Validate the GitHub App creation. We recommend that you choose a simple name for your GitHub app such as GitGuardian, which will make it easily recognizable.
- The GitHub App is now created and you can install it for users and organizations.
- Follow the exact same steps as for the GitHub.com SaaS integration.
The GitHub App belongs to the user who created it. We recommend that you transfer the ownership to an organization in case the user is later deactivated.
IMPORTANT: GitGuardian cannot monitor repositories whose owner has not installed the GitHub App. If the repo is owned by a GitHub organization, the owner of the organization must install the GitHub App.
Grant GitGuardian code write permissions
Some business features require write permissions to your repositories in order to open pull requests.
Currently, this concerns the Honeytoken Deployment jobs feature.
To allow GitGuardian to open pull requests on the repositories of your instance, go to the app settings page in GitHub, in the tab "Permissions & events". Under the "Repository permissions" section, change permissions on Contents to "Read and write":
This change then needs to be propagated to the organizations where this app is installed, by accepting the permission update request:
When you integrate your GitHub Enterprise instance, you have access to a configuration page.
From this page, you have the possibility to:
- integrate another GitHub Enterprise instance with GitGuardian.
- manage your existing instances and their dedicated GitHub app. GitGuardian tells you which ones are considered inactive.
Automatic historical scan
By default, GitGuardian performs a historical scan for each new GitHub Enterprise repository added to your perimeter.
You can deactivate this behavior in your GitHub Enterprise settings if you are a Manager of the workspace.