Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation updates an OAuth 2 application associated with a user. It allows modifying key properties of the OAuth 2 client application such as its name, confidentiality status, redirect URIs, and authorization behavior. This is useful in scenarios where you need to programmatically manage OAuth 2 clients for users, for example, updating client details after changes in your authentication setup or automating client management in a development workflow.

Practical examples include:

  • Changing the redirect URIs when your application's callback URLs change.
  • Updating the client name to reflect new branding.
  • Toggling whether the client is confidential (e.g., server-side vs public clients).
  • Adjusting secondary authorization requirements for enhanced security flows.

Properties

Name Meaning
Id The unique identifier of the OAuth 2 application to be updated.
Confidential Client Boolean flag indicating if the client is confidential (true) or public (false).
Name The display name of the OAuth 2 application.
Redirect Uris JSON array of redirect URIs registered for the OAuth 2 application.
Skip Secondary Authorization Boolean flag to skip the secondary authorization step during OAuth flows.

Output

The node outputs JSON data representing the updated OAuth 2 application object returned by the API. This typically includes all current properties of the OAuth 2 client after the update, such as its id, name, confidentiality status, redirect URIs, and authorization settings.

No binary data output is involved.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the target service's API.
  • The base URL for the API must be set in the credentials configuration.
  • The node uses HTTP requests to interact with the external API managing OAuth 2 applications.

Troubleshooting

  • Invalid Id: If the provided application ID does not exist, the API will likely return a "not found" error. Verify the ID before running the node.
  • Malformed Redirect URIs: The redirect_uris property expects valid JSON array format. Invalid JSON or incorrect URI formats may cause request failures.
  • Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions to update OAuth 2 applications.
  • Missing Required Fields: The Id field is mandatory; omitting it will prevent the update from proceeding.
  • Boolean Field Issues: Confirm boolean fields are properly set (true/false) to avoid unexpected behavior.

Links and References

Discussion