GitLab
Give Nebula access to GitLab projects, issues, merge requests and code search with a personal access token.
On this page
What it does
Nebula can read projects, issues and merge requests, and search code on GitLab, for example to trace a finding to the code that caused it.
Requirements
- A GitLab account with access to the projects Nebula should see.
- A personal access token with read scopes (
read_apiis usually enough).
Connect
- Create a personal access token in GitLab.
- In Settings, Integrations, choose GitLab and paste the token. BreachLine sends it as the
PRIVATE-TOKENheader and never shows it again.
Permissions and data handling
Nebula sees only what the token can see. Use a token from an account with the narrowest access that covers the work, and set an expiry.
Troubleshooting
| Symptom | Check |
|---|---|
401 from GitLab |
The token is valid and not expired. |
| Projects missing | The token’s account is a member of those projects. |
Known limitations
The connector calls the GitLab.com API (https://gitlab.com/api/v4). It has no setting for a self-managed GitLab instance’s address.