OAuth authorization
GitLab authorization uses OAuth with PKCE and provider-configured scopes rather than pasted credentials.
GitLab repository validation
Continuous GitLab repository security validation without changing your workflow.
Connect GitLab through OAuth, choose an accessible project and branch, and run supported code validations that feed the same fix queue, history, grade, and reports as GitHub evidence.
Definition
What this capability validates
GitLab support currently covers OAuth-authorized repository discovery, branch selection, public or private code validation, token refresh for scheduled work, and disconnect/revocation handling. It does not currently include GitLab configuration audit.
Current capability
Public and private projects
List and validate projects accessible to the authorized GitLab identity.
Branch-aware workflow
List available branches and validate the selected branch for supported code findings.
Manual and scheduled validation
Vault-held OAuth credentials can be refreshed for authorized scans that run later.
Scope and Limits
- GitLab OAuth access and refresh credentials are stored in Vault, with only a reference and metadata held in the application database.
- Disconnecting deletes the local Vault credential and attempts provider-side token revocation.
- GitLab repository configuration audit is not currently implemented.
Frequently Asked Questions
Can SecOpsium validate private GitLab projects?
Yes, when the connected GitLab identity and granted OAuth scope can access the project.
Are GitLab credentials stored?
OAuth access and refresh credentials are stored in Vault so authorized scans can refresh access. They are not stored directly in the application database.
Can GitLab validations be scheduled?
Yes. Supported scheduled code validations can use the connected GitLab project and branch.