GitLab
Integrate GitLab with Cloudaware to ingest groups, projects, and users for DevSecOps reporting and application correlation.
info
- Audience: Cloudaware administrators, DevOps
- Outcome: The GitLab account is connected, and GitLab groups, projects, and users are available in the CMDB for SDLC coverage and application correlation
Capabilities
The integration supports:
- Read-only discovery of GitLab groups, projects, and users in the CMDB
- Relationships between repositories, projects, applications, and related assets
- SDLC coverage and DevSecOps reporting in Cloudaware
Prerequisites
Before you begin, make sure you have:
- Access to a Cloudaware account.
- A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
- GitLab personal access token with read access.
- GitLab URL for self-managed GitLab instances, or the default GitLab SaaS URL.
Add a GitLab Account to Cloudaware
To connect your GitLab account to Cloudaware:
- In Cloudaware, go to Admin.
- Find GitLab Accounts, then click + ADD.
- Enter the following values:
- Name: A display name for this connection.
- Access Token: The GitLab personal access token.
- GitLab URL: The GitLab URL (typically,
https://gitlab.com/, a custom URL for a GitLab Self-Managed instance, orhttps://gitlab.{yourcompanyname}.comfor a GitLab Dedicated instance).
- Click SAVE.
- Confirm that the integration status indicator is green.
View GitLab Data in CMDB
To browse discovered GitLab resources:
- In Cloudaware, open CMDB Navigator.
- In the left pane, select GITLAB.
- Open an object list, e.g., GitLab Projects or GitLab Groups, to view records.
Supported Objects
Cloudaware ingests the following GitLab objects:
| GitLab Object | CMDB Object API Name |
|---|---|
| GitLab Account | CA10GL__CaGitLabAccount__c |
| GitLab Group | CA10GL__CaGitLabGroup__c |
| GitLab Project | CA10GL__CaGitLabProject__c |
| GitLab User | CA10GL__CaGitLabUser__c |
Troubleshooting
note
Initial data collection may take time to complete.
Authentication Fails or Integration Shows Red Status
- Verify that the GitLab access token is active and copied correctly.
- Confirm that the token has read access to the groups and projects Cloudaware must discover.
- For self-managed GitLab, confirm that the GitLab URL is correct and reachable.
- Re-enter the token by editing the integration in Cloudaware.
Projects or Groups Are Missing
- Confirm that the token owner can access the missing groups or projects in GitLab.
- Review token scopes and group-level access restrictions.
- In CMDB Navigator, verify that you are viewing the GITLAB section and related resources.
Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.
Reconfigure or Remove the Integration
warning
To rotate credentials, edit the existing integration instead of deleting and re-creating it.
Update the Integration Details
- Go to Admin.
- Select GitLab Accounts.
- Select the specific integration.
- Open the three-dot menu (⋮), then click Edit.
- Update the required fields.
- Click Save.
Remove the Integration from Cloudaware
- Go to Admin.
- Select GitLab Accounts.
- Select the specific integration.
- Open the three-dot menu (⋮), then click Delete.
- Confirm the deletion if prompted.
Security Notes
- Use a dedicated GitLab token for Cloudaware discovery.
- Grant only the minimum read scopes required for the groups, projects, and users Cloudaware must discover.
- Prefer token expiration where supported and rotate tokens according to your organization's policy.
- Avoid using personal administrator tokens for long-running integrations.
- Update the Cloudaware integration immediately if the token is revoked, regenerated, or expires.