AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node interacts with an Active Directory service to retrieve detailed information about groups. Specifically, it fetches group details based on a unique object identifier (Object Guid) within a specified company context. This operation is useful in scenarios where you need to programmatically access group metadata for user management, auditing, or synchronization tasks.

Practical examples include:

  • Fetching group membership details for access control automation.
  • Retrieving group attributes to sync with other identity management systems.
  • Auditing group configurations and memberships in bulk by applying query filters.

Properties

Name Meaning
Company Id Numeric identifier of the company to which the group belongs.
Object Guid Unique string identifier (GUID) of the group object to retrieve details for.
Source String indicating the source system or directory from which to retrieve the group details.
X USER ID User identifier sent as a header to authenticate or identify the requestor.
Additional Query Parameters Optional parameters to refine the query:
- Condition: Filter condition string.
- Skip: Number of records to skip.
- Limit: Maximum number of records to return.
- Order By: Field(s) to order the results by.

Output

The node outputs JSON data containing detailed information about the requested Active Directory group(s). The structure typically includes group attributes such as name, description, members, and other metadata fields returned by the Active Directory API.

If binary data were involved (e.g., group photos), it would be included in a separate binary output field, but this node focuses on JSON metadata output only.

Dependencies

  • Requires an API key credential for authentication with the Active Directory service.
  • Needs the base URL of the Active Directory API configured in the node credentials.
  • The node uses HTTP headers including a custom user ID header (X-USER-ID) for request identification.
  • No additional external libraries beyond the bundled OpenAPI client are required.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key and base URL are correctly configured in the node credentials.
  • Invalid Object Guid: If the provided GUID does not correspond to any group, the API may return a "not found" error. Verify the GUID value.
  • Insufficient permissions: The user identified by X-USER-ID must have permission to read group details; otherwise, authorization errors will occur.
  • Malformed query parameters: Incorrect values in additional query parameters like condition, skip, limit, or order_by can cause API errors. Validate these inputs carefully.
  • Network issues: Connectivity problems to the Active Directory API endpoint will result in request failures.

Links and References

Discussion