Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation, Retrieve Ad Gpos Details, is designed to fetch details about Group Policy Objects (GPOs) from an Active Directory environment. It is useful in scenarios where administrators or automation workflows need to query and analyze GPO configurations within a specific company domain. For example, it can be used to audit GPO settings, monitor changes, or integrate AD policy data into broader IT management systems.

Properties

Name Meaning
Company Id Numeric identifier of the company for which the GPO details are being retrieved.
Domains Id String identifier representing the domain within Active Directory to query.
Source Source parameter specifying the origin or context of the request.
X USER ID User identifier sent as a header to authenticate or track the request user.
Condition Optional query condition to filter or refine the GPO retrieval results.
Skip Number of records to skip in the result set, useful for pagination.
Limit Maximum number of records to return, controlling the size of the response.
Order By Field name(s) to order the results by, allowing sorted output based on specified criteria.

Output

The node outputs JSON data containing the details of the Active Directory GPOs matching the query parameters. The structure typically includes metadata about each GPO such as its identifiers, settings, and related attributes. There is no indication that binary data is returned by this operation.

Dependencies

  • Requires an API key credential to authenticate requests against the Connect Secure API.
  • Depends on the external Connect Secure service that exposes the Active Directory GPO details endpoint.
  • Proper configuration of the API credentials and network access to the Connect Secure API is necessary.

Troubleshooting

  • Common issues:
    • Missing or invalid API authentication token may cause authorization errors.
    • Incorrect or missing required properties like Company Id, Domains Id, or X USER ID will lead to request failures.
    • Network connectivity problems to the Connect Secure API endpoint can cause timeouts or connection errors.
  • Error messages:
    • Authorization errors typically indicate invalid or expired credentials; reconfigure the API key.
    • Validation errors suggest missing required parameters; ensure all mandatory fields are provided.
    • Rate limiting or quota exceeded errors require checking API usage limits or contacting the service provider.

Links and References

Discussion