Actions222
- Application Baseline Actions
- Attack Surface Actions
- Backup Software Actions
- EDR Actions
- Tags Actions
- PII Actions
- External Scan Actions
- Settings Actions
- Compliance Assessment Actions
- Reports Actions
- Compliance Actions
- Jobs Actions
- Active Directory Actions
- Retrieve Ad Roles
- Retrieve Ad User Licenses
- Retrieve Azure Licenses
- Retrieve Azure Ad Logs
- Retrieve Azure Secure Score
- Retrieve Ad Password Policies
- Retrieve Ad Groups View
- Retrieve Ad Ous View
- Retrieve Ad Gpos View
- Retrieve Ad Computers View
- Retrieve Ad Users View
- Retrieve Ad Domain Details
- Retrieve Ad Gpos Details
- Retrieve Get Ous Details
- Retrieve Get Groups Details
- Retrieve Ad Group Users
- Retrieve Ad Group Computers
- Retrieve Get User Details
- Retrieve Get Computer Details
- Retrieve Ad Roles Details
- Retrieve Ad Roles Member
- Retrieve Ad Basic Info
- Audit Log Actions
- Ad Audit Actions
- Asset Data Actions
- Retrieve Bios Info
- Retrieve Bio Info
- Retrieve Browser Extensions
- Retrieve Browser Extension
- Retrieve Ciphers View
- Retrieve Cipher View
- Retrieve Windows Protection Status
- Retrieve Window Protection Status
- Retrieve Asset Compliance Report Card
- Retrieve Asset Firewall Policy
- Retrieve Asset Installed Drivers
- Retrieve Asset Installed Driver
- Retrieve Asset Interface
- Retrieve Asset Msdt
- Retrieve Asset Ports
- Retrieve Asset Port
- Retrieve Asset Security Report Data
- Retrieve Asset Security Report Datum
- Retrieve Asset Shares
- Retrieve Asset Share
- Retrieve Asset Storages
- Retrieve Asset Storage
- Retrieve Asset Unqouted Services
- Retrieve Asset Unqouted Service
- Retrieve Asset User Shares
- Retrieve Asset User Share
- Retrieve Asset Video Info
- Retrieve Asset Windows Reboot Required
- Retrieve Asset Window Reboot Required
- Vulnerabilities Actions
- Firewall Actions
- Integration Actions
- Retrieve Integration Credentials
- Retrieve Integration Credential
- Create Integration Credential
- Update Integration Credential
- Delete Integration Credential
- Retrieve Integration Rules
- Retrieve Integration Rule
- Create Integration Rule
- Update Integration Rule
- Delete Integration Rule
- Retrieve Company Mappings
- Retrieve Company Mapping
- Create Company Mapping
- Update Company Mapping
- Delete Company Mapping
- Event Set Actions
- Ticket Template Actions
- Scheduler Actions
- Credentials Actions
- Asset Actions
- Retrieve Records
- Retrieve Assets
- Retrieve Asset
- Create Asset
- Update Asset
- Delete Asset
- Retrieve Asset Stats
- Retrieve Asset Stat
- Retrieve Asset View
- Retrieve Cron Jobs
- Retrieve Kernel Modules
- Retrieve Suid Permissions
- Retrieve Ufw Firewall Rules
- Retrieve Selinux Settings
- Retrieve Asset Iptables Rules
- Retrieve Asset Users
- Retrieve Asset Processes Running
- Retrieve Asset Services
- Retrieve Asset Patches Info
- Retrieve Asset Firewall Rules
- Retrieve Asset Registry Misconfiguration
- Retrieve Asset Open Ports
- Retrieve Notification Tickets View
- Retrieve System Events View
- Discovery Settings Actions
- Retrieve Discovery Settings
- Retrieve Discovery Setting
- Create Discovery Setting
- Update Discovery Setting
- Delete Discovery Setting
- Retrieve Agent Discoverysettings Mapping
- Retrieve Agent Discoverysetting Mapping
- Create Agent Discoverysetting Mapping
- Update Agent Discoverysetting Mapping
- Delete Agent Discoverysetting Mapping
- Auth Actions
- Company Actions
- Agent Actions
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-nodepackage 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