AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node interacts with the AvantGuard CIPP API to retrieve a list of sign-in records. It is designed to fetch sign-in data filtered by specific criteria such as whether the logon attempts failed, additional filter parameters, and tenant-specific filters. This node is useful in scenarios where you need to audit or monitor user sign-in activities, especially focusing on failed login attempts for security analysis or compliance reporting.

Practical examples include:

  • Retrieving all failed sign-in attempts within a tenant to identify potential unauthorized access.
  • Filtering sign-ins based on custom criteria to analyze user behavior or troubleshoot authentication issues.

Properties

Name Meaning
Failedlogononly A string value indicating whether to retrieve only failed logon attempts.
Filter A string used to apply additional filtering criteria to the sign-in list retrieval.
Tenantfilter A string specifying tenant-related filtering to scope the sign-in data to a particular tenant.

Output

The node outputs JSON data representing the list of sign-in records retrieved from the AvantGuard CIPP API. Each record typically contains details about individual sign-in events, such as timestamps, user identifiers, success or failure status, and other metadata as defined by the API response schema.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard CIPP API.
  • The base URL for the API is configured via credentials and appended with /api.
  • The node uses HTTP headers to accept and send JSON content (Accept: application/json, Content-Type: application/json).

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will result in authentication errors.
    • Improperly formatted filter strings may cause the API to reject the request or return no results.
    • Network connectivity issues can prevent successful API calls.
  • Error Messages:

    • Authentication failures typically indicate invalid or expired API keys; verify and update credentials.
    • API response errors related to query parameters suggest checking the syntax and validity of the Failedlogononly, Filter, and Tenantfilter values.
    • Timeout or connection errors require ensuring network access to the configured API endpoint.

Links and References

Discussion