Security & Identity · Integration
LDAP
Add LDAP to your product for your customers, and give your AI agents governed access to it.
Embed an LDAP integration so your customers can point your product at the directory they already run instead of maintaining a second list of users. Each customer supplies their own directory endpoint and bind credentials, so reads and writes happen under the permissions of that bind and every call is recorded. fastn handles connection setup, credential storage, paging over large result sets and upkeep, so a customer with an unusual schema needs no code from you.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own directory so your product authenticates and looks up their users.
Search entries under a base DN with a filter so your product finds only the records it needs.
Read group membership so your product decides what a user is allowed to see.
Create or modify entries and attributes where the bind account is permitted to write.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent looks up a user's groups and attributes before answering an access question.
An agent adds or removes a group member after an approval, within governed permissions.
Every bind, search and write is scoped per tenant and logged, so a change can be traced to its source.
Example prompt
Search the directory for accounts in the sales organisational unit and list the groups each one belongs to.
Set up LDAP in 4 steps
- 01Open the LDAP connector from your fastn dashboard.
- 02Have each customer supply their own directory endpoint and bind credentials.
- 03Map the base DNs, object classes and attributes your product uses, then enable actions.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the LDAP integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an LDAP integration without building it. Your customers point it at their own endpoint and credentials and work their users, groups and roles through it, with no per-customer code on your side.
- Handle the part that actually costs time: the blast radius of an error is large, so least-privilege and auditability are non-negotiable. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an LDAP update is not your on-call problem.
- One integration serves your product and your agents. The same governed LDAP connection powers in-product features and gives AI agents scoped, audited access, so you keep access and identity in step across a customer's estate without wiring it twice.
Used by these teams
Compare with
Okta
Microsoft Entra IDWorks well with
Google WorkspaceOften used alongside
Tools the same teams tend to run next to LDAP, across other categories.
ServiceNow
Datadog
PagerDuty
AWS CloudWatchLDAP integration FAQ
How do I add an LDAP integration to my product?
Enable the LDAP connector in your fastn dashboard, then let each customer authenticate their own LDAP account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LDAP client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
How is an LDAP connection configured per customer?
LDAP is a specification rather than a service you sign up for, so there is no LDAP account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own users, groups and roles. The per-tenant isolation works the same way it does for a vendor product.
Can AI agents use this LDAP integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent looks up a user's groups and attributes before answering an access question.
Who maintains the LDAP integration?
fastn does. When LDAP changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
What permissions does the LDAP integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own LDAP tenant, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source.
Can access changes be automated safely?
Yes. Provisioning and deprovisioning can be driven from your product or an agent within governed permissions, with every action audited, which is what makes automated access changes reviewable after the fact.
What can I build with the LDAP integration?
A common starting point: connect their own directory so your product authenticates and looks up their users. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the LDAP integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LDAP does not change your per-connector cost. You can start free with 3 connected accounts.
Add LDAP to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.