Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve information about a specific firewall user. It is designed to fetch detailed data for a given user ID within a firewall context. This functionality is useful in scenarios where network administrators or security teams need to programmatically access user details from their firewall system, such as auditing user access, monitoring user activity, or integrating firewall user data into other systems.

For example, you might use this node to:

  • Automatically pull user details when a security alert is triggered.
  • Sync firewall user information with an internal user management database.
  • Generate reports on firewall user activity by retrieving user info on demand.

Properties

Name Meaning
X USER ID The unique identifier of the user making the request; sent as a header named X-USER-ID.
Id The numeric identifier of the firewall user whose details are being retrieved.

Output

The node outputs JSON data representing the firewall user's details as returned by the Connect Secure API. The exact structure depends on the API response but typically includes user attributes such as username, roles, status, and other relevant metadata.

If the API supports binary data (e.g., user certificates or profile images), the node would include this in the binary output field, but based on the provided code and properties, the primary output is JSON user data.

Dependencies

  • Requires an active connection to the Connect Secure API.
  • Needs an API authentication token or key configured in the node's credentials (referred generically as "an API key credential").
  • The node uses the OpenAPI specification bundled internally to define its operations and properties.

Troubleshooting

  • Missing or invalid X USER ID header: Ensure that the X USER ID property is correctly set and passed as a header; otherwise, the API may reject the request.
  • Invalid or missing Id parameter: The firewall user ID must be a valid number corresponding to an existing user; incorrect IDs will result in errors or empty responses.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions to access firewall user data.
  • Network or connectivity issues: Confirm that the n8n instance can reach the Connect Secure API endpoint without firewall or proxy restrictions.

Links and References

Discussion