AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve multi-factor authentication (MFA) user information filtered by a tenant identifier. It is designed to fetch a list of MFA users associated with a specific tenant, which can be useful for security audits, user management, or compliance reporting within an organization.

A practical example use case would be automating the retrieval of MFA-enabled users for a particular tenant in a multi-tenant environment, enabling administrators to monitor and manage access controls efficiently.

Properties

Name Meaning
Tenantfilter A required string used as a query parameter to filter the MFA users by tenant identifier.

Output

The node outputs JSON data containing the list of MFA users corresponding to the specified tenant filter. The structure typically includes user details relevant to MFA status and identification within that tenant.

If binary data were involved, it would represent related files or attachments, but this node focuses on JSON responses from the API.

Dependencies

  • Requires an API key credential for authenticating requests to the AvantGuard CIPP API.
  • The base URL for the API is configured via credentials and appended with /api.
  • Uses the @avantguardllc/n8n-openapi-node package to build properties and handle API interactions.
  • The node expects the API to respond with JSON-formatted data.

Troubleshooting

  • Missing or invalid tenant filter: Since the tenant filter is required, omitting it or providing an incorrect value will likely result in errors or empty results. Ensure the tenant filter string is valid and correctly formatted.
  • Authentication errors: If the API key credential is missing, expired, or invalid, the node will fail to authenticate. Verify the API key and its permissions.
  • API connectivity issues: Network problems or incorrect base URL configuration can cause request failures. Confirm the API endpoint URL and network accessibility.
  • Unexpected API responses: Changes in the API schema or server errors may lead to unexpected output or errors. Check the API documentation and server status if issues arise.

Links and References

Discussion