Skip to main content
Use the @bijection/connectors/ldap entrypoint to declare LDAP and Active Directory resources.

Availability

This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.

Resources and modes

Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.

Directory entries

incremental: incremental

The following example matches configuration standard.

Configuration: standard

Case: ldap/directory/incremental/standard. Connection and resource configuration are declared by this exact case. Credential kind: ldap. Keep credential material in the private credential inventory.
Native admission analysis is available for this exact declaration. Collection: entries
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. Run bijection ldap serve --config bridge.json next to the directory and expose it through an authenticated HTTPS ingress. The bridge holds the bind DN and password, uses LDAPS or StartTLS, and keeps no state. Bind the resource’s endpoint to the ingress URL and install the bridge’s bearer as an ldap credential (ldap.credential). The bridge’s mode selects change tracking:
  • dirsync: Active Directory DirSync with tombstones for deleted objects (needs “Replicating Directory Changes” on the naming context root).
  • usn: Active Directory uSNChanged windows on one domain controller plus the Deleted Objects container for tombstones. A new DC invocation id resets.
  • snapshot: any LDAPv3 directory. Each pass is a new paged baseline, and an entry that baseline does not return leaves.
Entries are keyed by objectGUID or entryUUID, carry the DN, the configured version attribute and the configured attributes as text lists. The snapshot holds at most maxEntries (default 50000, at most 131072). An entry that moves out of the base DN or stops matching the filter gets no tombstone; in the Active Directory modes the bridge forces a new baseline once the current one is older than rebaseline_hours (default 24), and that baseline withdraws it. A 410 from the bridge restarts the baseline. No real directory has been reached by these checks.

Provider references

Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.

Source and evidence

Canonical connector source, native analysis and check receipts. Connector artifact: 905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305. The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.