Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node interacts with the Connect Secure API to retrieve firewall user information. Specifically, the "Retrieve Firewall Users" operation fetches a list of users from the firewall system based on various query parameters such as filtering conditions, pagination controls, and sorting preferences.

Common scenarios for this node include:

  • Auditing or monitoring firewall user access.
  • Integrating firewall user data into security dashboards or reports.
  • Automating user management workflows by retrieving current firewall user details.

For example, you might use this node to get all firewall users who meet certain criteria (e.g., active status), skip the first 10 records, limit the results to 50 users, and order them by username.

Properties

Name Meaning
X USER ID The User Id header value required for authentication or identification in the request.
Condition A query string to filter the firewall users based on specific conditions.
Skip Number of records to skip in the result set (used for pagination).
Limit Maximum number of records to return (used for pagination).
Order By Field name(s) to order the returned firewall users by (e.g., username, date created).

Output

The node outputs JSON data representing the retrieved firewall users. Each item in the output corresponds to a firewall user record matching the query parameters. The structure typically includes user attributes as provided by the Connect Secure API.

If the API supports binary data for this operation (not indicated here), it would be summarized accordingly, but this operation primarily returns JSON user data.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • Depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: Since the X USER ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure this property is correctly set.
  • Invalid query parameters: Incorrect values in condition, skip, limit, or order_by may lead to API errors or empty results. Validate these inputs carefully.
  • API connectivity issues: Network problems or incorrect API credentials can cause failures. Verify network access and credential validity.
  • Pagination mishandling: Setting skip or limit improperly might result in unexpected subsets of data. Use these parameters according to your data retrieval needs.

Links and References

Discussion