Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Roles Member under the Active Directory resource, is designed to query and retrieve members associated with Active Directory roles. It allows users to specify filtering conditions, pagination controls, and sorting options to tailor the results. This is particularly useful in scenarios where an organization needs to programmatically access role membership information from their Active Directory for auditing, reporting, or synchronization purposes.

For example, a company might use this node to:

  • Fetch all members of a specific AD role identified by its Object Guid.
  • Retrieve a paginated list of role members with custom filtering conditions.
  • Sort the retrieved members based on certain attributes.

Properties

Name Meaning
Company Id The unique identifier of the company within which the Active Directory roles exist.
Object Guid The globally unique identifier (GUID) of the Active Directory object (role) to query.
X USER ID The user identifier used for authentication or tracking purposes in the request header.
Condition Optional query condition string to filter the results based on specific criteria.
Skip Number of records to skip for pagination purposes.
Limit Maximum number of records to return in the response.
Order By Field(s) by which to order the returned results.

Output

The node outputs JSON data representing the members of the specified Active Directory role. The structure typically includes details about each member such as identifiers, names, and possibly other attributes depending on the API's response schema.

If binary data were involved (e.g., profile pictures), it would be indicated here, but this operation focuses on JSON data retrieval only.

Dependencies

  • Requires an active connection to the Connect Secure API that exposes the Active Directory endpoints.
  • Needs an API key or token credential configured in n8n to authenticate requests.
  • The X USER ID header must be provided to identify the user making the request.
  • The node depends on the external service's availability and correct configuration of company and object GUID parameters.

Troubleshooting

  • Missing or invalid credentials: Ensure the API key/token is correctly set up in n8n credentials.
  • Invalid Object Guid or Company Id: Verify that the GUID and company ID correspond to existing entities in the Active Directory system.
  • Empty or no results: Check the Condition, Skip, and Limit parameters to ensure they are not overly restrictive.
  • API rate limits or connectivity issues: Confirm network connectivity and API usage limits.
  • Incorrect X USER ID header: Make sure the user ID is valid and authorized to perform the query.

Links and References

Discussion