Gitea icon

Gitea

Interact with Gitea via API

Actions393

Overview

This node operation allows you to list the keys associated with a specific user in a Gitea instance. It is useful for managing and auditing SSH or GPG keys tied to user accounts, which are often used for authentication and secure access to repositories. For example, an administrator can retrieve all keys for a user to verify authorized access or revoke outdated keys.

Properties

Name Meaning
Username The username of the user whose keys you want to list. This is a required string input.
Fingerprint (Optional) Filter keys by their fingerprint value.
Page (Optional) The page number of results to return, starting at 1. Used for pagination.
Limit (Optional) The maximum number of results to return per page.

Output

The output will be a JSON array containing key objects related to the specified user. Each object typically includes details such as the key's ID, type, fingerprint, and creation date. This structured data enables further processing or display within workflows.

No binary data output is expected from this operation.

Dependencies

  • Requires connection to a Gitea API endpoint.
  • Needs an API authentication token configured in the node credentials to authorize requests.
  • The base URL for the Gitea instance must be provided in the credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing username will cause the request to fail.
    • Incorrect API credentials or insufficient permissions may result in authorization errors.
    • Pagination parameters (page and limit) set incorrectly (e.g., zero or negative values) might lead to unexpected results or empty responses.
  • Error messages:

    • 401 Unauthorized: Check that the API token is valid and has sufficient permissions.
    • 404 Not Found: Verify the username exists in the Gitea instance.
    • 400 Bad Request: Ensure query parameters like page and limit are positive integers.

Links and References

Discussion