AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve kernel module information related to assets. Specifically, the "Get Retrieve Kernel Modules" operation fetches details about kernel modules associated with a given user context. This can be useful in scenarios where you need to audit or monitor kernel modules loaded on devices managed by AvantGuard, for security assessments, compliance checks, or troubleshooting system configurations.

Practical examples include:

  • Fetching kernel module data for a specific user to verify installed modules.
  • Applying query filters to limit or order the results based on conditions such as module name or load time.
  • Skipping a number of records and limiting the output size for pagination purposes.

Properties

Name Meaning
X USER ID The User Id header value used to specify the user context for which kernel modules are retrieved. This is required.
Additional Query Parameters Optional parameters to refine the query:
- Condition: A query condition string to filter results.
- Skip: Number of records to skip (for pagination).
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data containing the retrieved kernel modules information. Each item in the output corresponds to a kernel module record matching the query parameters and user context. The structure typically includes fields describing the kernel module's properties such as name, version, status, and other metadata as provided by the AvantGuard API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard ConnectSecure API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request building and execution.

Troubleshooting

  • Missing or invalid X USER ID: Since the user ID header is required, omitting it or providing an incorrect value will likely cause authentication or authorization errors. Ensure the correct user ID is supplied.
  • API connection issues: Network problems or incorrect base URL configuration can lead to failed requests. Verify API endpoint accessibility and credential correctness.
  • Invalid query parameters: Providing malformed or unsupported query conditions may result in API errors. Validate query syntax and parameter values.
  • Empty results: If no kernel modules match the query, the output will be empty. Adjust query parameters or check if the user has associated kernel modules.

Links and References

Discussion