All articles
These Keycloak guides cover the decisions that connect identity design to day-to-day operation: realm boundaries, application clients, token contents, sessions, reverse proxies, and resource sizing. Each article works from official project documentation and identifies the configuration choices behind the behavior an application sees.
Begin with realms, clients, and token design when deciding which users belong together, how applications receive permissions, or where token lifetimes differ from session limits. The guide also covers the master realm and the boundaries of exporting configuration between environments.
For login failures after introducing a reverse proxy, the hostname and proxy error guide connects symptoms to public URLs, forwarding headers, and client redirect settings. Use that reference to establish the deployment's URL configuration before interpreting its resource needs.
The memory and heap sizing guide separates documented baselines from workload calculations. Follow it into the session sizing calculator to vary planning inputs. If the identity platform is still undecided, the Keycloak, authentik, and Authelia comparison explains the protocols, user backends, and deployment components behind that choice.
-
Keycloak Behind a Reverse Proxy: Fix 403 and Hostname Errors
Why Keycloak returns 403 behind a proxy, rejects redirect URIs, and issues tokens with the wrong issuer, and the exact options that resolve each case.
-
Keycloak Memory Usage and Heap Sizing Explained
Keycloak hardware requirements explained: RAM baselines, JVM heap and container limits, Infinispan session caches, and CPU sizing from login rates.
-
Keycloak vs authentik vs Authelia: What to Self-Host
A protocol, architecture and footprint comparison of three self-hosted identity servers, and the deployment shapes each one is actually built for.
-
Keycloak Realms Explained: Clients, Roles and Tokens
What a Keycloak realm isolates, when to use one or several realms, and how clients, roles, scopes, sessions and tokens fit together.