Hello
Currently, the GitLab plugin in Digital.ai Release only supports authentication using an API key. However, starting from GitLab version 16.x, API tokens have a maximum expiration period of 365 days. This poses a challenge for our institutionalized environment with over 1000 connections, as it would require frequent token updates.
-Proposed Solution
To bypass this issue, we propose using username and password authentication for the GitLab plugin, similar to how it is already implemented for version control (Git server connection). This would eliminate the need for frequent token updates and provide a more sustainable authentication solution for our large-scale environment.
Regards
by: Mahdi S. | about a month ago | Integrations
Comments
The GitLab plugin in Digital.ai Release interacts with GitLab using its REST API. Since the GitLab API does not support basic authentication (username and password), GitLab recommends using access tokens for security reasons.