Connector library

Implemented source Enterprise, ERP & HR APIs

Active Directory connector.

Read selected Active Directory rootDSE, immediate-child organizational-unit and group references over authenticated LDAPS through three named actions.

Connector download

Download Active Directory

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.0 Choose version
Release
2026-10-04
Package
Implemented source
Schema credentials
Basic auth
Connection settings
Directory Host, Directory Port, Operation Timeout (ms)
Package size
9 KB
SHA-256
993f3c5dc1583e4bb29fe50109bab365e7a893f12a7e3be033937c98edf66a34

Version history

What's new

  1. v0.2.0.0Latest · 2026-10-04 · Implemented source

    Read selected Active Directory rootDSE metadata and first native pages of immediate-child OU/group DN/name references over authenticated LDAPS through three named actions.

  2. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical readable HTTP scaffold, retained unchanged.

Included in this version

Included actions

Implemented in v0.2.0.0. Use a separate flow trigger; no webhook trigger is included.

Get directory information

Read selected rootDSE naming contexts, directory DNS name and advertised LDAP versions.

List organizational units

Read a first bounded page of selected OU DN/name references immediately below the explicit search base.

List groups

Read a first bounded page of selected group DN/common-name references immediately below the explicit search base.

Vendor API

API and access

Implementation considerations
  • Directory metadata: Read selected rootDSE naming contexts, directory DNS name and advertised LDAP versions.
  • Organizational-unit references: Read the first native page of selected OU DNs and name values immediately below an explicit search base.
  • Group references: Read selected group DNs and common-name values without members, nested membership or account changes.
  • Caller-managed reads; no account writes, membership changes or directory event triggers are included.
  • Use an approved directory DNS hostname and LDAPS listener, default port 636, with normal certificate/hostname verification and TLS 1.2 or newer. A managed Basic Auth credential carries the full bind DN as username and password as password; it supplies an LDAP simple bind, not an HTTP header. Node.js 22 or newer, pinned ldapts support and outbound trusted LDAPS must be available in the executor. No anonymous/SASL/UPN bind, plaintext or StartTLS/TLS-bypass fallback is exposed.
  • List actions use one-level scope, fixed object-class filters, selected name attributes and no alias dereferencing. Maximum Entries requests 1–100 records in the first native RFC 2696 page, default 100. The iterator is closed before another page, then the session unbinds. Short or empty pages do not prove complete coverage; no total, ordering or continuation cookie is exposed. Referrals and excessive/malformed results fail without truncation.
  • Native sizeLimit is zero so the SDK preserves server size-limit errors; paging supplies the requested reference-page size and local checks enforce selected-result limits. DN spelling and multivalue names retain Unicode and zeroes; no case-folded DN equivalence is inferred. User records, contacts, group members and security descriptors are omitted. Advertised metadata does not certify health, permissions or forest coverage.
  • Operation Timeout is 1000–8000 ms per connection/protocol operation, default 5000; it is not an overall action deadline. A 256 KiB selected-result cap applies after SDK decode, not as a hard wire-byte or decoder-memory ceiling. Automatic rebind is disabled, bound state is checked before/after reading and failed public-unbind cleanup suppresses success. Earlier HTTP scaffold mappings require deliberate migration; hosted runtime/import and live certificate/account/ACL/paging remain untested.
  • Three packaged native LDAPS reads select rootDSE metadata and first-page OU/group references. Microsoft/RFC contracts and the pinned SDK establish behavior; executor runtime/LDAPS trust and live directory/account/ACL/paging require validation.

Support

Need help with Active Directory?

Tell us what you need to connect or change.