GitLab API

GitlabTool
Join our community

Actions905

Overview

This node operation retrieves a specific impersonation token for a user from the GitLab API. It is useful for administrators or automation workflows that need to manage or audit user impersonation tokens, which allow acting on behalf of a user. For example, it can be used to verify the details of a token before revoking it or to fetch token metadata for security audits.

Use Case Examples

  1. Fetch impersonation token details for a user to verify token permissions.
  2. Retrieve token information to audit user access in GitLab.

Properties

Name Meaning
Skip Authentication If true, the node will skip using authentication credentials for the API request.
Authentication The authentication method used for the API request, typically an API key credential.
baseUrl The base URL of the GitLab instance to which the API request is sent.
Method The HTTP method used for the API request, here it is GET to retrieve data.
Path Parameters Parameters used in the API request path to specify the user ID and impersonation token ID to retrieve.

Output

JSON

  • id - The unique identifier of the impersonation token.
  • name - The name of the impersonation token.
  • scopes - The scopes or permissions granted to the impersonation token.
  • created_at - The timestamp when the impersonation token was created.
  • expires_at - The expiration date of the impersonation token.
  • active - Indicates whether the impersonation token is currently active.

Dependencies

  • GitLab API authentication credential

Troubleshooting

  • Ensure the user ID and impersonation token ID are correct and exist in the GitLab instance.
  • Verify that the API authentication credentials have sufficient permissions to access user impersonation tokens.
  • Check the base URL to confirm it points to the correct GitLab instance.
  • Common error messages include 404 Not Found if the user or token does not exist, and 401 Unauthorized if authentication fails.

Links

Discussion