# Identity and Access Management Architecture

DevFeed: [Identity and Access Management Architecture](<https://devfeed.tech/articles/identity-and-access-management-architecture-103394.md>)

Original publisher: [Read original article](<https://blog.devops.dev/identity-and-access-management-architecture-ad5dde7e7765?source=rss----33f8b2d9a328---4>)

Author: Scaibu

Published: 2026-10-27T10:20:02Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Keycloak](<https://devfeed.tech/topics/keycloak.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [OpenID connect (OIDC)](<https://devfeed.tech/topics/oidc.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [sessions](<https://devfeed.tech/topics/sessions.md>), [saml](<https://devfeed.tech/topics/saml.md>), [WebAuthn](<https://devfeed.tech/topics/webauthn.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [ami](<https://devfeed.tech/tags/ami.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [broker](<https://devfeed.tech/tags/broker.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-and-access](<https://devfeed.tech/tags/identity-and-access.md>), [identity-and-access-management](<https://devfeed.tech/tags/identity-and-access-management.md>), [jwt](<https://devfeed.tech/tags/jwt.md>), [keycloak](<https://devfeed.tech/tags/keycloak.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [login](<https://devfeed.tech/tags/login.md>), [lts](<https://devfeed.tech/tags/lts.md>), [minors](<https://devfeed.tech/tags/minors.md>), [oauth2](<https://devfeed.tech/tags/oauth2.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [password](<https://devfeed.tech/tags/password.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [system-design-interview](<https://devfeed.tech/tags/system-design-interview.md>)

## AI overview

Keycloak centralizes login, federation and token issuance, while applications validate signed JWTs locally and retain fine-grained authorization such as tenant roles, API keys and resource permissions. The excerpt recommends coarse roles and identity claims in short-lived tokens, with per-request tenant membership checks and ReBAC in the application. It describes an integration that gets PKCE and five-minute access tokens right but has critical gaps: its JWT verifier decodes tokens without checking signatures, and sign-in and administration still use the legacy password grant. The target design uses Authorization Code with PKCE for people, client credentials for services, device authorization for CLIs, and cached JWKS validation checking signature, issuer, audience and expiry. Keycloak is presented as feature-rich for self-hosted federation and security controls, but requires operating a stateful Java service and keeping pace with quarterly upgrades; it does not replace application-level authorization.

## Source excerpt

A Practical Guide to Authentication, Authorization, Single Sign-On, and Identity FederationWhat Keycloak is? Keycloak is an open-source identity broker and authorization server: it logs users in, issues standards-based tokens, and federates identities from other systems so your services never handle passwords. The current release is 26.8.1, shipped 13 October 2026 (versio.io). It solves three problems at once. Applications delegate login to one place (SSO). Users can come from local accounts, LDAP/AD, or upstream IdPs such as Google or a corporate SAML IdP (brokering and federation). Services verify a signed JWT locally instead of calling a session store on every request. Key facts that shape how you operate it: Lineage. Red Hat has stewarded it since 2018 and ships it commercially as Red Hat build of Keycloak; it is a CNCF incubating project. Runtime. Since version 17 it runs on Quarkus, not WildFly. Old guides using standalone.xml, /auth context paths or jboss-cli are obsolete. No LTS. The community project patches only the latest minor; older lines stop getting security fixes when a new one ships (Skycloak). Minors land roughly quarterly (26.5 Jan, 26.6 Apr, 26.7 Jul, 26.8 Oct 2026), so plan an upgrade cadence, not an install. Admin bootstrap changed. KEYCLOAK_ADMIN / KEYCLOAK_ADMIN_PASSWORD were replaced by KC_BOOTSTRAP_ADMIN_USERNAME / KC_BOOTSTRAP_ADMIN_PASSWORD, which seed a temporary first admin only Core domain model Everything in Keycloak lives inside a realm, a fully isolated namespace with its own users, clients, keys and login policies. The master realm is for administering Keycloak only; never put application users there. Realm. Isolation boundary for users, keys, sessions and flows. Use one realm per trust domain, not per customer; hundreds of realms degrade startup and the admin UX. Client. An application that asks Keycloak to authenticate users or itself. Public clients (SPA, mobile) hold no secret; confidential clients (backends) hold a secret or k