AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the "Application Baseline" resource to retrieve application baseline rules. It is designed to fetch rules that define baseline configurations or policies for applications, which can be useful in security monitoring, compliance checks, or configuration management scenarios. For example, a user might use this node to get the current baseline rules applied to an application environment to verify compliance or audit changes.

Properties

Name Meaning
X USER ID User Id (string) - Required header to identify the user making the request.
Additional Query Parameters Optional query parameters to refine the retrieval:
- Condition (string): Query condition to filter results.
- Skip (number): Number of records to skip (for pagination).
- Limit (number): Maximum number of records to return.
- Order By (string): Field(s) to order the results by.

Output

The node outputs JSON data representing the retrieved application baseline rules. Each item in the output corresponds to a rule matching the query parameters and user context. The structure typically includes details about each baseline rule such as identifiers, conditions, and metadata. There is no indication that binary data is returned by this node.

Dependencies

  • Requires an API key credential for authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • The node uses HTTP headers and query parameters to communicate with the external API endpoint.

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 authorization errors. Ensure the user ID is correctly set.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in empty responses or errors from the API.
  • API connectivity issues: Network problems or incorrect base URL configuration can prevent successful requests.
  • Pagination misconfiguration: Setting skip or limit incorrectly could lead to unexpected subsets of data or no data returned.

Links and References

Discussion