GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node interacts with the GitLab API to revoke a user's GPG key by its ID. It is useful in scenarios where a user needs to invalidate a previously added GPG key for security or administrative reasons. For example, if a GPG key is compromised or no longer in use, this node can be used to revoke it programmatically within an automation workflow.

Use Case Examples

  1. Revoking a compromised GPG key for a user in GitLab.
  2. Automating the cleanup of old or unused GPG keys in a GitLab user account.

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, defaulting to https://gitlab.com.
Method HTTP method to use for the request, default is GET but POST is used for revoking the GPG key.
Path Parameters Parameters to be included in the request path, specifically the GPG key ID to revoke.

Output

JSON

  • statusCode - HTTP status code of the revoke request response
  • body - Response body from the GitLab API after revoking the GPG key

Dependencies

  • GitLab API credentials for authentication

Troubleshooting

  • Ensure the provided GPG key ID is valid and exists for the user.
  • Check that the GitLab API credentials have sufficient permissions to revoke GPG keys.
  • Verify the base URL is correct for the GitLab instance being accessed.
  • Common error: 404 Not Found if the key ID does not exist or is not accessible.
  • Common error: 401 Unauthorized if authentication fails or credentials are missing.

Links

Discussion