AvantGuard - DNSFilter icon

AvantGuard - DNSFilter

AvantGuard - DNSFilter

Actions277

Overview

This node integrates with the AvantGuard DNSFilter API to retrieve a list of agent local users. Specifically, the "Agent Local User Index" operation fetches multiple local user records from the system, optionally filtered and sorted by various query parameters. This is useful in scenarios where you need to audit, monitor, or manage local users associated with agents in your network security environment.

Practical examples include:

  • Listing all local users currently registered on agents.
  • Filtering users by name or organization to focus on specific groups.
  • Paginating through large sets of users for reporting or synchronization purposes.
  • Sorting users alphabetically by name.

Properties

Name Meaning
Additional Query Parameters Optional filters and controls for the query:
- In A Collection (boolean): Filter users that belong to a collection.
- Name (string): Filter by user name; searches friendly_name or user_name.
- Organization Ids (JSON array): Filter by one or more organization IDs; defaults to the user's organization.
- Page (JSON object): Pagination details such as page number and size.
- Search (string): Search filter by name or user login.
- Sort (string): Sort results by valid attributes like name.

Output

The node outputs JSON data representing the list of agent local users retrieved from the API. Each item in the output typically contains user details such as names, identifiers, organization affiliations, and other metadata as provided by the API response.

If binary data were involved (e.g., files or attachments), it would be indicated here, but this operation deals solely with JSON user data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard DNSFilter service.
  • The node uses the base URL https://api.dnsfilter.com for API requests.
  • No additional external dependencies are required beyond the API access.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Invalid query parameters: Passing malformed JSON or unsupported values in the additional query parameters may cause request failures. Validate JSON syntax and parameter types.
  • Empty results: If no users are returned, verify that the filters applied (e.g., organization IDs, search terms) match existing data.
  • API rate limits: Excessive requests might be throttled by the service; implement retries or backoff if needed.

Links and References

Discussion