Keycloak features

Keycloak capabilities that buyers evaluate one at a time, from SCIM provisioning and user lifecycle workflows to FAPI security profiles and FIPS mode.

Keycloak SCIM user and group provisioning

Provisioning users and groups into Keycloak from HR systems or identity governance tools through its SCIM API: what the implementation covers, service account permissions, and how SCIM attributes map to the user profile.

Keycloak token exchange (RFC 8693)

Exchanging one token for another in Keycloak: what the supported standard token exchange covers, what still needs the deprecated legacy version, and patterns for service-to-service delegation.

Keycloak FAPI 2.0, DPoP and CIBA

Using Keycloak for financial-grade APIs: FAPI 1.0 and 2.0 profiles enforced through client policies, sender-constrained tokens with DPoP, pushed authorization requests and decoupled CIBA authentication.

Keycloak as an MCP authorization server

Securing Model Context Protocol servers and AI agents with Keycloak: supported MCP versions, resource indicators, client ID metadata documents and the experimental features to enable.

Keycloak FIPS 140-2 mode

Running Keycloak in FIPS 140-2 mode for regulated environments: the BouncyCastle FIPS libraries, non-strict versus strict mode, keystore and key length limits, and features such as Kerberos that do not work under FIPS.

Keycloak Kerberos and SPNEGO desktop SSO

Transparent sign-in from domain-joined desktops through Kerberos and SPNEGO in Keycloak, how it combines with LDAP or Active Directory federation, and its incompatibility with FIPS mode.

Talk to our team.

Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.

  • 30-minute call: free, with no obligation.
  • NDA on request: we can sign before you share details.
  • Clear next steps: a scope and plan after the call.