GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation revokes a GPG key for a specified user in GitLab. It is useful for managing user security by invalidating GPG keys that should no longer be trusted or used. For example, an administrator can revoke a compromised or outdated GPG key associated with a user account.

Use Case Examples

  1. Revoke a GPG key for a user by specifying the user ID and the GPG key ID to enhance account security.
  2. Automate the process of invalidating GPG keys when users leave an organization or change their security credentials.

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 to which the request is sent.
Method The HTTP method used for the request, defaulting to POST for this operation.
Path Parameters Parameters included in the request path to identify the user and the GPG key to revoke.

Output

JSON

  • success - Indicates whether the GPG key revocation was successful.
  • message - Additional information or confirmation message about the revocation process.

Dependencies

  • GitLab API authentication token or credentials

Troubleshooting

  • Ensure the user ID and GPG key ID are correct and exist in the GitLab instance to avoid 404 errors.
  • Authentication errors may occur if the API token is missing, expired, or lacks sufficient permissions; verify the API credentials.
  • Network or base URL misconfiguration can cause connection failures; confirm the baseUrl is correct and accessible.

Links

Discussion