GitLab API icon

GitLab API

Gitlab

Actions880

Overview

This node operation revokes tokens for a specified top-level group in GitLab by making a POST request to the GitLab API endpoint `/api/v4/groups/{id}/tokens/revoke`. It is useful for managing group access tokens, especially when you need to invalidate tokens for security or administrative purposes.

Use Case Examples

  1. Revoke all tokens for a specific GitLab group by providing the group's ID.
  2. Automate token revocation as part of a security compliance workflow.

Properties

Name Meaning
Skip Authentication Determines whether to skip authentication for the request.
Authentication Specifies the authentication method to use, defaulting to GitLab API authentication.
baseUrl The base URL of the GitLab instance, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but can be set to POST, PUT, DELETE, HEAD, or PATCH.
Path Parameters Parameters to be included in the request path, specifically the group ID to identify the top-level group whose tokens are to be revoked.

Output

JSON

  • statusCode - HTTP response status code from the API request
  • body - Response body returned by the GitLab API after revoking tokens

Dependencies

  • GitLab API authentication credentials

Troubleshooting

  • Ensure the group ID provided in the path parameters is valid and corresponds to a top-level group in GitLab.
  • Verify that the authentication credentials are correctly configured and have sufficient permissions to revoke tokens for the group.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.
  • Common error messages may include 401 Unauthorized if authentication fails, 404 Not Found if the group ID does not exist, or 403 Forbidden if the user lacks permission to revoke tokens. Resolving these involves verifying credentials, group ID, and user permissions.

Discussion