GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to rotate a personal access token for a specific group. It is useful for automating the process of renewing access tokens to maintain security without manual intervention. For example, it can be used in workflows that require periodic token rotation for group access in GitLab.

Use Case Examples

  1. Automate rotation of group access tokens to enhance security.
  2. Integrate token rotation into CI/CD pipelines to ensure tokens are always up to date.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request.
Authentication Type of authentication used, here it is GitLab API authentication.
baseUrl The base URL of the GitLab instance to which the request is sent.
Method HTTP method used for the request.
Path Parameters Parameters included in the request path, specifically the group ID for which the token rotation is performed.

Output

JSON

  • id - The ID of the rotated access token.
  • name - The name of the access token.
  • scopes - The scopes or permissions granted to the access token.
  • created_at - Timestamp when the access token was created.
  • expires_at - Timestamp when the access token will expire.
  • token - The new access token string after rotation.

Dependencies

  • GitLab API credentials for authentication

Troubleshooting

  • Ensure the group ID provided in the path parameters is correct and exists in GitLab.
  • Verify that the API credentials have sufficient permissions to rotate access tokens for the group.
  • Check the base URL to ensure it points to the correct GitLab instance.
  • If authentication is skipped, the request will likely fail unless the GitLab instance allows unauthenticated access for this operation.

Links

Discussion