GitLab API icon

GitLab API

Gitlab

Actions917

Overview

This node interacts with the GitLab API to retrieve details of a specific impersonation token for a user. It is useful in scenarios where you need to programmatically access or audit impersonation tokens associated with GitLab users, such as in administrative or security automation workflows.

Use Case Examples

  1. Retrieve impersonation token details for a user to verify token permissions or expiration.
  2. Automate auditing of user impersonation tokens in GitLab for compliance purposes.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the API request.
Authentication Specifies the authentication method to use, typically an API key credential for GitLab.
baseUrl The base URL of the GitLab instance to which the API requests are sent.
Method The HTTP method used for the API request, defaulting to GET.
Path Parameters Parameters used in the API request path to specify the user ID and impersonation token ID.

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 creation timestamp of the impersonation token.
  • 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 path parameters are correctly set and correspond to existing resources in GitLab.
  • Verify that the API authentication token has sufficient permissions to access user impersonation tokens.
  • Check the baseUrl to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages may include 404 Not Found if the user or token ID does not exist, or 401 Unauthorized if authentication fails. Verify credentials and permissions to resolve these errors.

Links

Discussion