AvantGuard - ConnectSecure icon

AvantGuard - ConnectSecure

AvantGuard - ConnectSecure

Actions223

Overview

This node operation retrieves members of Active Directory roles based on specified criteria. It is useful in scenarios where you need to query and list users or entities assigned to particular AD roles within a company environment. For example, an IT administrator might use this node to fetch all members of a specific security group or role to audit permissions or manage access control.

Properties

Name Meaning
Company Id The unique identifier of the company for which the AD roles members are being retrieved.
Object Guid The GUID (Globally Unique Identifier) of the Active Directory object (role/group) to query.
X USER ID The user ID header value used for authentication or identification in the request.
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 output JSON contains the data returned from the Active Directory API call that lists the members of the specified AD role. This typically includes details about each member such as their identifiers, names, and possibly other attributes depending on the API response. The node does not explicitly handle binary data output.

Dependencies

  • Requires an API key credential for authenticating requests to the Active Directory service.
  • Needs proper configuration of the base URL for the Active Directory API endpoint.
  • The node uses HTTP query parameters and headers to send requests, including a custom header for user identification.

Troubleshooting

  • Missing or invalid Company Id/Object Guid: Ensure these required fields are correctly provided; otherwise, the API will likely return errors or empty results.
  • Authentication errors: If the X USER ID header or API credentials are incorrect or missing, the request will fail with authorization errors.
  • Query parameter issues: Incorrectly formatted conditions or unsupported query parameters may cause the API to reject the request.
  • Empty results: Could be due to no members matching the criteria or incorrect GUIDs.

Links and References

Discussion