Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ufw Firewall Rules under the Asset resource, is designed to fetch firewall rules configured in a UFW (Uncomplicated Firewall) system via an API. It allows users to query and retrieve specific firewall rule data based on various filtering and pagination parameters.

Typical use cases include:

  • Automating the retrieval of firewall rules for auditing or compliance checks.
  • Integrating firewall rule data into monitoring dashboards.
  • Filtering and exporting firewall rules based on conditions or sorting preferences.

For example, a user might want to retrieve all firewall rules that match a certain condition, skip the first 10 records, limit the output to 50 entries, and order them by creation date.

Properties

Name Meaning
X USER ID User identifier required for authentication or scoping the request.
Condition Query condition to filter firewall rules (e.g., status, IP address).
Skip Number of records to skip from the start of the result set (for pagination).
Limit Maximum number of records to return (for pagination).
Order By Field name(s) to order the results by (e.g., "created_at", "priority").

Output

The node outputs JSON data representing the retrieved UFW firewall rules. Each item in the output typically corresponds to a firewall rule with its associated properties such as rule ID, source/destination IPs, ports, action (allow/deny), and other metadata depending on the API response.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Connect Secure API.
  • The node depends on the external Connect Secure API endpoint that exposes UFW firewall rules.
  • Proper network connectivity and API access permissions are necessary.
  • 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 in "Condition", "Skip", "Limit", or "Order By" may cause errors or empty responses. Validate these inputs.
  • API authentication errors: If the API key credential is missing or expired, authentication will fail.
  • Network issues: Connectivity problems to the API endpoint can cause timeouts or failures.
  • Empty results: If no firewall rules match the given condition or if pagination skips past available records, the output may be empty.

Links and References

Discussion