Gitea icon

Gitea

Interact with Gitea via API
Join our community

Actions393

Overview

This node operation allows creating a new OAuth 2 application for a user in the target system. It is useful when you want to programmatically register OAuth 2 clients, for example, to enable third-party applications or services to authenticate via OAuth 2 on behalf of users.

Common scenarios include:

  • Automating the setup of OAuth 2 clients during onboarding processes.
  • Managing multiple OAuth 2 applications without manual intervention.
  • Integrating with systems that require dynamic OAuth client registration.

Practical example: Automatically create an OAuth 2 application with specified redirect URIs and client confidentiality settings whenever a new user is onboarded.

Properties

Name Meaning
Confidential Client Boolean flag indicating if the OAuth 2 client is confidential (true) or public (false).
Name The name assigned to the OAuth 2 application/client.
Redirect Uris JSON array of redirect URIs that the OAuth 2 application will use after authentication.
Skip Secondary Authorization Boolean flag to skip secondary authorization steps during OAuth 2 flow (true/false).

Output

The node outputs JSON data representing the created OAuth 2 application details as returned by the API. This typically includes identifiers, client secrets (if applicable), configured redirect URIs, and other metadata about the OAuth 2 client.

If binary data were involved (not indicated here), it would represent files or attachments related to the OAuth 2 application, but this node focuses on JSON output only.

Dependencies

  • Requires an API key or token credential to authenticate requests against the target system's API.
  • The base URL for the API must be configured in the node credentials.
  • The node uses HTTP requests with JSON payloads to interact with the API endpoint responsible for OAuth 2 application creation.

Troubleshooting

  • Invalid Redirect URIs: Ensure the redirect URIs are valid URLs and properly formatted as a JSON array.
  • Authentication Errors: Verify that the API key or token used has sufficient permissions to create OAuth 2 applications.
  • Missing Required Fields: The "Name" property should not be empty; provide a meaningful name for the OAuth 2 client.
  • API Endpoint Issues: Confirm the base URL and API version are correct in the credentials configuration.

Common error messages might include unauthorized access, invalid input format, or server errors. Resolving these usually involves checking credentials, input data formatting, and API availability.

Links and References

Discussion