AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve SELinux settings related to assets. It is designed to fetch security context configurations or policies applied on assets managed by the AvantGuard system. This can be useful in scenarios where you need to audit, monitor, or analyze SELinux settings for compliance or troubleshooting purposes.

For example, a security engineer might use this node to programmatically pull SELinux configurations across multiple assets to verify that security policies are consistently applied.

Properties

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

Output

The node outputs JSON data representing the retrieved SELinux settings for the specified assets. The structure corresponds to the API response from the AvantGuard ConnectSecure service and typically includes details about SELinux contexts, rules, or policies associated with the assets.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure API authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in credentials.
  • Uses the @avantguardllc/n8n-openapi-node package internally to build properties and handle requests.
  • The node sends HTTP requests with headers including X-USER-ID and expects JSON responses.

Troubleshooting

  • Missing or invalid X USER ID: The node requires a valid user ID header; ensure it is provided and correctly formatted.
  • API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Query parameter issues: Incorrect values for condition, skip, limit, or order_by may cause empty or error responses; validate these inputs.
  • Network or connectivity problems: Ensure the base URL is reachable and the network allows outbound connections to the AvantGuard API.
  • Unexpected API response structure: If the API changes, the node's output format may differ; check for updates or adjust downstream processing accordingly.

Links and References

Discussion