Skip to main content

2 posts tagged with "standards"

View All Tags

SCIM Explained: What It Is, When You Need It, and How Keycloak Does It

· 7 min read
GR Patil
GR Patil
Phase Two

SCIM — System for Cross-domain Identity Management — is a standard REST API for creating, updating, and deactivating user accounts across systems. SSO answers "can this person log in?" SCIM answers "does this person have an account at all, and should they still?"

If you sell to enterprises, you will be asked for it. This post covers what it is, when you actually need it, and a working walkthrough of Keycloak's native SCIM API — which arrived as a preview feature and is not enabled by default.

Everything here was run against Keycloak 26.7.3.

Why your startup should use Keycloak for SSO and User Management - Part 1: Standards

· 4 min read
GR Patil
GR Patil
Phase Two
note

In this series we are proposing Keycloak as a superior alternative to commercial identity offerings.

Part 1: Standardized Protocols and Minimal Feature Set Differentiation​

In the realm of Identity and Access Management (IAM) solutions, it's essential to recognize that many offerings, both commercial and open source, operate on standardized protocols such as OpenID Connect (OIDC), Security Assertion Markup Language (SAML), System for Cross-domain Identity Management (SCIM), Lightweight Directory Access Protocol (LDAP), and more. This adherence to standardized protocols often results in minimal differentiation at the feature set level across various options. Let's delve into this further: