GitLab API icon

GitLab API

Gitlab
Join our community

Actions880

Overview

This node operation renews the secret of a specific application in GitLab by making a POST request to the endpoint `/api/v4/applications/{id}/renew-secret`. It is useful for scenarios where the application's secret key needs to be refreshed for security reasons or to reset credentials.

Use Case Examples

  1. Renew the secret of a GitLab application by providing its ID to enhance security.
  2. Automate the process of rotating application secrets in GitLab to comply with security policies.

Properties

Name Meaning
Skip Authentication Option to skip authentication for the request, useful for testing or public endpoints.
Authentication Type of authentication used, default is GitLab API key authentication.
baseUrl Base URL of the GitLab instance, default is https://gitlab.com.
Method HTTP method to use for the request, default is GET but for this operation it should be POST.
Path Parameters Parameters to be included in the request path, specifically the application ID to identify which application's secret to renew.

Output

JSON

  • id - The ID of the application whose secret was renewed.
  • secret - The new secret generated for the application.

Dependencies

  • GitLab API key credential for authentication

Troubleshooting

  • Ensure the application ID provided in the path parameters is correct and exists in GitLab.
  • Verify that the API key used for authentication has sufficient permissions to renew application secrets.
  • If skipping authentication, confirm that the GitLab instance allows unauthenticated requests for this endpoint, otherwise the request will fail.
  • Common error messages include 401 Unauthorized (invalid or missing API key), 404 Not Found (application ID does not exist), and 403 Forbidden (insufficient permissions).

Links

Discussion