Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Asset Iptables Rules, is designed to fetch iptables rules associated with a specific asset from an external API. It allows users to query and retrieve firewall or network filtering rules configured for assets, which can be useful in scenarios such as security audits, compliance checks, or automated network management.

Practical examples include:

  • Automatically retrieving current iptables rules for an asset before applying changes.
  • Integrating asset firewall configurations into monitoring dashboards.
  • Filtering and exporting iptables rules based on conditions or pagination parameters.

Properties

Name Meaning
X USER ID User identifier required for authentication or scoping the request.
Condition Query condition string to filter the iptables rules returned by the API.
Skip Number of records to skip (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved iptables rules for the specified asset. The structure typically includes an array of rule objects, each describing individual iptables entries such as source/destination addresses, ports, protocols, and actions.

If binary data were involved (e.g., exporting rules as files), it would be indicated here, but this operation focuses on JSON data output.

Dependencies

  • Requires an API key or token credential to authenticate requests to the Connect Secure API.
  • Depends on the external Connect Secure API service being available and accessible.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: The API may reject requests without a valid user ID header. Ensure the "X USER ID" property is correctly set.
  • Invalid query parameters: Incorrect values for condition, skip, limit, or order_by may cause errors or empty responses. Validate these inputs.
  • API connectivity issues: Network problems or incorrect credentials will result in failed requests. Verify API access and credentials.
  • Pagination mishandling: Setting skip and limit incorrectly might lead to unexpected subsets of data.

Common error messages might include authorization failures, bad request due to malformed query parameters, or server errors indicating API downtime.

Links and References

Discussion