Integrating Bridgecrew with Github Server makes it possible for Bridgecrew to scan your Infrastructure-as-code files (Terraform and CloudFormation) and monitor configuration issues in development.
For details on integrating Bridgecrew with Github.com, see here.
IP-based Network Access
If your organization requires IP-based access to its network, add all three IP addresses below to your ingress access configuration.
If you've set custom rules to use Github Enterprise's built-in firewall (see more here), you must whitelist the IP addresses below.
For Prisma cloud console integration - discover relevant IP addresses here
For Bridgecrew platform - Bridgecrew performs load balancing across these addresses.
- From Integrations Catalogue, under Code Integrations, select GitHub Server .
- Enter your GitHub Server domain, for example, github.my_company.com, then select Register. A new tab opens for registering a new OAUTH app on GitHub Server.
- Copy Application Name, Homepage URL and Authorization Callback URL from the Register OAUTH app step.
- Paste the copied values for Application Name, Homepage URL and Authorization Callback URL from the Register OAUTH app step and select Register Application.
The details of the new OAUTH app appear and Bridgecrew opens in a new tab.
|Application Name||For example, Bridgecrew|
|Authorization Callback URL||https://www.bridgecrew.cloud/api/v1/integrations/githubEnterprise|
- . Copy the Client ID and Client Secret values.
Paste copied values for Client ID and Client Secret (from GitHub Server, as shown above) and select Authorize.
Within the same tab, you are redirected back to GitHub Server.
Select Authorize Bridgecrew
You are then redirected back to Bridgecrew on the same tab.
- Select one of the following options then select Next:
- Permit all existing repositories
- Permit all existing and future repositories
- Choose from the repository list.
If choosing from the repository list, select the relevant repositories.
- When the message "New account successfully configured" appears, select Done.
Note: after the next GitHub Server scan, the scanned repository will appear in the Integrations grid; for further details, see here.
Updated 10 months ago