AvantGuard - CIPP icon

AvantGuard - CIPP

AvantGuard - CIPP

Actions136

Overview

This node integrates with the AvantGuard CIPP API to perform operations related to session management within a specified list resource. Specifically, the "Retrieve Exec Revoke Sessions" operation allows users to query and retrieve information about revoked execution sessions filtered by tenant and session ID. This can be useful in scenarios where administrators need to audit or manage session revocations for security or compliance purposes.

Practical examples include:

  • Fetching details of revoked sessions for a particular tenant to monitor unauthorized access attempts.
  • Integrating session revocation data into workflows that trigger alerts or further automated actions when certain sessions are revoked.

Properties

Name Meaning
Id The unique identifier of the session to retrieve.
Tenantfilter A filter string specifying the tenant scope to narrow down the session retrieval query.

Output

The node outputs JSON data representing the details of the revoked execution sessions matching the provided Id and Tenantfilter. The structure typically includes session metadata such as session identifiers, timestamps, status, and possibly user or tenant-related information depending on the API response.

No binary data output is indicated for this operation.

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 used as the request base path.
  • The node depends on the @avantguardllc/n8n-openapi-node package for building properties and handling OpenAPI-based requests.
  • The OpenAPI specification (openapi.json) defines the available resources and operations.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key credential is correctly set up and has sufficient permissions to access the session revoke endpoints.
  • Invalid or missing parameters: Both Id and Tenantfilter are required; omitting them will likely cause errors or empty responses.
  • Network or API errors: Check connectivity to the configured API base URL and verify that the API service is operational.
  • Unexpected response format: If the API changes or returns unexpected data, verify the OpenAPI spec version matches the deployed API.

Links and References

Discussion