GitLab API icon

GitLab API

Gitlab
Join our community

Actions917

Overview

This node operation retrieves the GPG keys of a specific user from the GitLab API (version 4). It is useful for scenarios where you need to access or manage a user's GPG keys, such as verifying commit signatures or managing user security settings. For example, an admin might use this to audit or display a user's GPG keys in an internal dashboard.

Use Case Examples

  1. Retrieve GPG keys for a user with ID 123 to verify their commit signatures.
  2. List all GPG keys for a user to manage or audit security credentials.

Properties

Name Meaning
Skip Authentication Whether to skip authentication 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.
Query Parameters Optional query parameters for pagination, including page number and items per page.
Path Parameters Path parameters specifying the user ID whose GPG keys are being retrieved.

Output

JSON

  • id - The unique identifier of the GPG key.
  • key - The actual GPG public key string.
  • created_at - Timestamp when the GPG key was created.
  • expires_at - Timestamp when the GPG key expires, if applicable.
  • can_edit - Indicates if the GPG key can be edited.
  • user_id - The ID of the user to whom the GPG key belongs.

Dependencies

  • GitLab API authentication token or API key credential

Troubleshooting

  • Ensure the user ID path parameter is correctly set and is a valid integer; otherwise, the API will return an error.
  • Check that the authentication token or API key is valid and has sufficient permissions to access user GPG keys.
  • If pagination parameters (page, per_page) are used, verify they are valid integers to avoid request errors.

Links

Discussion