GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation retrieves a specific GPG key of a user from the GitLab API. It is useful for scenarios where you need to access or verify a user's GPG key details, such as in security audits or user management tasks within GitLab.

Use Case Examples

  1. Fetch the GPG key details of a user by providing the user ID and the GPG key ID to verify the key's authenticity or status.
  2. Use this operation to integrate GitLab user GPG key information into a custom dashboard or reporting tool.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for public or unauthenticated access scenarios.
Authentication Specifies the authentication method to use, defaulting to GitLab API credentials.
baseUrl The base URL of the GitLab instance to which the request is sent, defaulting to https://gitlab.com.
Method HTTP method to use for the request, defaulting to GET.
Path Parameters Parameters to specify the user ID and the GPG key ID for the request.

Output

JSON

  • id - The unique identifier of the GPG key.
  • key - The actual GPG key string.
  • created_at - Timestamp when the GPG key was created.
  • expires_at - Timestamp when the GPG key expires, if applicable.
  • can_encrypt - Indicates if the key can be used for encryption.
  • can_sign - Indicates if the key can be used for signing.
  • can_certify - Indicates if the key can be used for certification.
  • can_authenticate - Indicates if the key can be used for authentication.

Dependencies

  • GitLab API credentials

Troubleshooting

  • Ensure the user ID and GPG key ID are correct and exist in the GitLab instance to avoid 404 Not Found errors.
  • If authentication is enabled, verify that the GitLab API credentials are valid and have sufficient permissions to access user GPG keys.
  • Check the base URL to ensure it points to the correct GitLab instance, especially if using a self-hosted GitLab server.

Links

Discussion