App service
Services/Keycloak

Keycloak service

Self-hosted Keycloak identity service for application authentication and single sign-on, with linked PostgreSQL storage.

Use it as a reusable, versioned service inside custom or predefined stacks so teams can keep the runtime and operational model consistent.

On Wodby

How Keycloak runs on Wodby

What Wodby sets up for Keycloak on this service. Keycloak runs from the official quay.io/keycloak/keycloak image in production mode (start). Configuration is passed as KC_* environment variables.

Linked services

LinkVariables
PostgreSQL (required)KC_DB_URL_HOST, KC_DB_URL_PORT, KC_DB_URL_DATABASE, KC_DB_USERNAME, KC_DB_PASSWORD

KC_DB is set to postgres. All Keycloak data is in that database: the service has no volume.

What the manifest sets

  • KC_HOSTNAME is the service's URL in the environment. Keycloak uses it for the addresses it issues, such as token issuers and redirects.
  • TLS ends at Wodby's router: KC_HTTP_ENABLED is true and KC_PROXY_HEADERS is xforwarded.
  • KC_HEALTH_ENABLED and KC_METRICS_ENABLED are true. Health and metrics are served on the management port 9000, which is private; the application port is 8080.

First administrator

KC_BOOTSTRAP_ADMIN_USERNAME and KC_BOOTSTRAP_ADMIN_PASSWORD come from the service tokens admin_username and admin_password. Keycloak uses them only when it creates the master realm, on the first start with an empty database, and marks the account as temporary. Changing the tokens later does not change an existing account.

Changing configuration

Add or change KC_* environment variables on the service and deploy it. Environment variables take precedence over conf/keycloak.conf, which is not on a volume. Realms, clients and users are managed in the administration console or its API and stored in the database.

Check the result

From inside the environment, /health/ready on port 9000 is the readiness endpoint the service itself is probed with.

Overview

Technical profile and packaging

This page shows how Keycloak is packaged and versioned as a Wodby service, what it exposes at runtime, and which source artifacts it builds on.

Service type

App service

Versions

26.8

Ports and protocols

8080/HTTP, 9000/HTTP

Labels

keycloak, identity, authentication

Stacks

Use it inside ready-made stacks or your own

These public stacks already include Keycloak as part of their default service model. You can start there and customize the stack, or compose your own stack around the same building block.

Runtime wiring

Reuse connectivity, storage, and runtime defaults

This service can expose ports, connect to other services, attach persistent storage, and define runtime defaults that become reusable inside stacks rather than being rebuilt case by case.

Endpoints

8080/HTTP, 9000/HTTP

Technical domains

HTTP endpoints from this service can use technical domains with auto-renewed TLS certificates on Wodby.

Service links

These links define which other services can connect to Keycloak when it is used inside a stack.

Derived services

Build your own service on top of Keycloak

These services already extend Keycloak. They show how the same base runtime can be turned into more specialized building blocks without rebuilding everything from scratch.