Gatekeeper to Ldap integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Gatekeeper and Ldap: authenticate both systems, choose the objects to sync (such as Gatekeeper's Vendors (Suppliers) and Files), map fields visually, and changes propagate both ways in milliseconds — no code required.

Change detection on Gatekeeper: No native developer webhook subscription API and no database change-data-capture log; detect changes by polling the JSON:API list endpoints filtered and sorted on updated-at timestamps. Gatekeeper's own event automation - Workflow Engine phase transitions and Interconnect process orchestration - runs inside the platform rather than as a subscribable webhook stream. On Ldap: No universal native change feed. Incremental sync polls the modifyTimestamp operational attribute (or entryCSN / uSNChanged on servers that expose them) for entries changed since the last cursor; detecting deletes needs a server changelog or tombstones because a plain search cannot see removed entries. Some servers add Persistent Search or RFC 4533 content-sync (syncrepl), but that support is server-specific. No webhooks. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.

On the Gatekeeper side: Categories, Contracts, Vendors (Suppliers), Files, plus custom fields where Gatekeeper exposes them. On the Ldap side: Schema (subschema subentry), Entries, Person entries (inetOrgPerson / user), Groups (groupOfNames / posixGroup). Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Gatekeeper and Ldap: Where Ldap tracks engineering work: requests become issues; Where Ldap moves messages between services: activity lands on the stream; Where Ldap is the directory or identity source: one set of users. A ticket or request raised in Gatekeeper opens or updates a matching issue in Ldap, and status, comments, and resolution flow back, so support and engineering work the same item instead of retyping it.

Gatekeeper: RESTful API following the JSON:API specification, tenant-scoped with interactive docs at {tenant}.gatekeeperhq.com/api_docs and a published Postman collection. The API is dynamic: it exposes the standard Contract and Vendor objects plus any custom data groups and workflow-form data configured in the tenant. Authentication: API keys created and managed under Configuration > API Keys and passed as a token; each key carries granular per-endpoint permissions set to read-only or write, so access is scoped per object. Multiple keys can be issued and revoked independently. Ldap: LDAPv3 protocol (RFC 4511) over TCP, typically LDAPS on port 636 or StartTLS on 389; reaches any LDAPv3 directory server - OpenLDAP, Microsoft Active Directory, 389 Directory Server, Oracle Unified Directory, PingDS/ForgeRock, NetIQ eDirectory, Apache Directory. Authentication: A bind DN and password (simple bind), typically over TLS, using a service account with rights to the target subtree. SASL mechanisms - GSSAPI/Kerberos, DIGEST-MD5, or EXTERNAL with a client certificate - are available where the server supports them. Stacksync manages authentication, retries, and rate limits on both sides.