AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with the AvantGuard ConnectSecure API to retrieve Suid permissions related to assets. Specifically, the "Get Retrieve Suid Permissions" operation fetches permission details for a given user ID (SUID) on assets. This is useful in scenarios where you need to audit or verify what permissions a particular user has on various assets within your system.

Practical examples include:

  • Checking access rights of a user before performing asset modifications.
  • Generating reports on user permissions for compliance audits.
  • Integrating permission checks into automated workflows to enforce security policies.

Properties

Name Meaning
X USER ID The User ID (SUID) for which permissions are being retrieved.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip.
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data containing the Suid permissions associated with the specified user ID. The structure typically includes permission details per asset, such as access levels and any relevant metadata returned by the API.

If binary data were involved, it would be summarized here, but this node focuses on JSON permission data only.

Dependencies

  • Requires an API key credential for AvantGuard ConnectSecure API authentication.
  • Needs the base URL of the AvantGuard ConnectSecure API configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

  • Missing or invalid User ID: Ensure the "X USER ID" property is provided and correctly formatted; otherwise, the API will reject the request.
  • API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Query parameter issues: Incorrectly formatted or unsupported query parameters may cause errors or unexpected results.
  • Network or connectivity problems: Confirm that the base URL is reachable from the n8n instance.

Common error messages might include unauthorized access, bad request due to invalid parameters, or timeout errors. Resolving these involves checking credentials, input values, and network connectivity.

Links and References

Discussion