Security & Identity · Integration
Keycloak
Add Keycloak to your product for your customers, and give your AI agents governed access to it.
Embed a Keycloak integration so your customers can let your product manage their own identity server instead of an admin working through the console. Each customer grants access to their own realm with only the scopes the actions you enable require, permissions are scoped per tenant, and every call is recorded so an access change can be traced to its source. That is what makes automated provisioning reviewable after the fact.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers create, update, enable, or disable their own Keycloak users from inside your product.
Read realms, clients, groups, and roles so your product mirrors each customer's access model.
Assign or remove a role or group membership when a permission changes in your product.
Read a user's roles and group membership to decide what they may see in your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent checks a user's roles and groups before answering an access question.
An agent enables or disables an account within governed permissions, with each action audited.
An agent grants a role after an approval, so the change is attributable to the request behind it.
Example prompt
List users in this realm with an admin role and show which groups grant it.
Set up Keycloak in 4 steps
- 01Open the Keycloak connector from your fastn dashboard.
- 02Have each customer authenticate their own Keycloak server with least-privilege client credentials.
- 03Map the realms, clients, roles, and user fields 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 Keycloak integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Keycloak integration without building it. Your customers connect their own Keycloak account inside your product and work their users, groups and roles there, 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 a Keycloak update is not your on-call problem.
- One integration serves your product and your agents. The same governed Keycloak 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
Auth0
Okta
OneLoginOften used alongside
Tools the same teams tend to run next to Keycloak, across other categories.
ServiceNow
Datadog
PagerDuty
AWS CloudWatchKeycloak integration FAQ
How do I add a Keycloak integration to my product?
Enable the Keycloak connector in your fastn dashboard, then let each customer authenticate their own Keycloak account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Keycloak client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Keycloak account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Keycloak account and only ever sees their own users, groups and roles. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Keycloak 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 checks a user's roles and groups before answering an access question.
Who maintains the Keycloak integration?
fastn does. When Keycloak 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 Keycloak integration need?
Only the scopes required for the actions you enable. Each customer grants access to their own Keycloak 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 Keycloak integration?
A common starting point: create, update, enable, or disable their own Keycloak users from inside your product. 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 Keycloak integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Keycloak does not change your per-connector cost. You can start free with 3 connected accounts.
Add Keycloak to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.