AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node integrates with the AvantGuard CIPP API to retrieve information about users who have been disabled from executing certain actions. Specifically, the "Retrieve Exec Disable User" operation under the "List" resource fetches details about a user’s execution disable status based on provided parameters. This can be useful in scenarios where administrators need to audit or verify which users are restricted from executing commands or accessing specific functionalities within a system.

Practical examples include:

  • Checking if a particular user is currently disabled from executing commands.
  • Filtering disabled users by tenant or enable status for compliance reporting.
  • Automating alerts or workflows when a user’s execution privileges change.

Properties

Name Meaning
Enable A required string parameter used as a query filter to specify the enable status.
Id A required string parameter representing the unique identifier of the user to retrieve.
Tenantfilter A required string parameter used as a query filter to specify the tenant scope.

Output

The node outputs JSON data containing the retrieved user information related to their execution disable status. The exact structure depends on the API response but typically includes user identifiers, enable status, tenant information, and possibly metadata about the disablement.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • Needs the base URL of the AvantGuard resource API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties and handling API communication.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key and base URL are correctly set up in the node credentials.
  • Required parameters not provided: The node requires Enable, Id, and Tenantfilter parameters; missing any will cause errors.
  • API connectivity issues: Network problems or incorrect API URLs may result in failed requests.
  • Unexpected API responses: If the API changes or returns errors, verify the parameters and consult the API documentation.

Links and References

Discussion