Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node provides an authorization mechanism for the "Auth" resource with the "Authorize" operation. It is designed to authenticate requests by sending a client authentication token in the request headers. This token is expected to be a base64-encoded string combining tenant, client ID, and client secret information.

Common scenarios where this node would be beneficial include:

  • Integrating with APIs that require client credentials passed as a base64-encoded token in the header.
  • Automating authentication flows where the client token needs to be dynamically set or rotated.
  • Acting as a preliminary step in workflows that require authorized access to protected resources.

For example, you might use this node to authorize access to a secure API by providing the encoded client credentials, enabling subsequent nodes to perform authenticated operations.

Properties

Name Meaning
Client Auth Token A required string representing the client authentication token. It must be base64-encoded in the format (tenant+client_id:client_secret). This token is sent in the request header Client-Auth-Token.

Output

The node outputs data through its main output channel. The exact structure of the JSON output is not explicitly defined in the provided source code, but typically it would contain the response from the authorization endpoint, such as tokens or status messages confirming successful authorization.

No binary data output is indicated or handled by this node.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the external Connect Secure API service.
  • Uses the @devlikeapro/n8n-openapi-node package and an OpenAPI specification (openapi.json) to build properties and handle operations.
  • The user must provide a valid base64-encoded client authentication token.

Troubleshooting

  • Invalid or missing Client Auth Token: If the token is not provided or incorrectly formatted, the authorization will fail. Ensure the token is base64-encoded correctly as (tenant+client_id:client_secret).
  • Authentication errors from the API: These may occur if the token is expired, revoked, or incorrect. Verify credentials and regenerate the token if necessary.
  • Network or connectivity issues: Failures to reach the Connect Secure API can cause errors. Check network settings and API availability.
  • Misconfiguration of credentials: Ensure the API key credential is properly configured in n8n.

Links and References

  • Base64 Encoding
  • Documentation for the Connect Secure API (not provided here; refer to your API provider's official docs)
  • n8n documentation on Credentials and HTTP Request Node for general guidance on API authentication patterns

Discussion