GitLab is an incredibly popular DevOps software package that aims to unify teams and simplify the development process. Exporting issues detected in Intruder to GitLab makes it easier for your teams to have all the information they need for their workflows in one place.
You can also choose to use a custom GitLab domain if you use a non-standard GitLab domain within your company.
This integration supports both GitLab.com and self-hosted GitLab instances.
Connect to GitLab
To connect Intruder to your GitLab account, first create a Personal Access Token in GitLab. This token requires the
apiscope. You can do this in Preferences > Access Tokens and checking the 'api' checkbox
With your token ready, head to the Integrations Page in the Intruder portal and press the green Add button on the GitLab tab.
Enter your token in the window that appears. If you're using self-hosted GitLab, enter the domain of your GitLab instance in the Host section, e.g.
gitlab.example.com.
Once you've added the API Token and pressed 'Connect', you can select a project to create issues in and choose if you want GitLab issues to be created automatically when Intruder discovers them.
Click "Test integration" and you'll see an issue appear in the project you selected.
Manually export issues to GitLab
To manually export an issue to GitLab, go to the Issues page and simply click the GitLab icon.
Automatically create GitLab issues
Head to Settings > Integrations > GitLab and check the checkbox next to "Automatically create issues for Low/Medium/High/Critical severity threats and above". You can also choose the severity filter for the issues you want to export to GitLab.
Troubleshooting
If you have any problems, ensure that your GitLab instance is accessible to the public Internet so that Intruder can communicate with it.
The GitLab integration is only available to Cloud, Pro, Enterprise, and Vanguard users