Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node operation allows users to retrieve Active Directory password policies via an API. It is useful in scenarios where administrators or security teams need to programmatically access and audit password policy settings from Active Directory environments. For example, it can be used to fetch current password complexity requirements, expiration settings, or lockout policies to ensure compliance with organizational security standards.

Properties

Name Meaning
X USER ID User Id header value sent with the request, typically identifying the requester.
Condition Query condition to filter the password policies returned by the API.
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 representing the retrieved Active Directory password policies. Each item in the output corresponds to a password policy record matching the query parameters. The structure depends on the API response but generally includes fields describing password complexity, expiration, lockout thresholds, and other relevant policy details.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API endpoint that exposes Active Directory password policy information.
  • Proper configuration of the API credentials within n8n is necessary for successful requests.

Troubleshooting

  • Common Issues:
    • Missing or invalid API authentication token may cause authorization errors.
    • Incorrect or malformed query conditions could lead to empty results or API errors.
    • Pagination parameters (skip and limit) set improperly might result in unexpected subsets of data.
  • Error Messages:
    • Authorization failures typically indicate issues with the provided API key or user ID header.
    • Validation errors from the API may occur if query parameters are not formatted correctly.
  • Resolutions:
    • Verify that the API key credential is correctly configured and active.
    • Ensure the "X USER ID" property is set with a valid user identifier.
    • Double-check query syntax and parameter values for correctness.

Links and References

Discussion