Skip to main content

Keycloak (keycloak)

OpenID Connect provider of the platform: realm enterprise-ai with the portal, control-plane and cli clients, federation with the bank directory (LDAP or Entra ID).

Generated from catalog/services/keycloak.yaml: do not edit by hand.

Summary​

Version26.8.1
Useinstall and configure, configure and connect
Layerfunctional (AI catalog)
CategoryIdentity and secrets
Installation methodsbinary, podman
External connectionno
Sandbox onlyno

Licence​

SPDX identifierApache-2.0
Licence policycore licence (MIT or Apache-2.0)
Licence exception-
Platform componentkeycloak

Packages and artifacts​

A package the project of the service publishes (its image, its binary archive, its Python or OS package) carries the licence of the service; a third-party package carries the licence written on its row, read from the official upstream metadata.

KindPackageVersionLicenceDetails
container imagequay.io/keycloak/keycloak26.8.1Apache-2.0image key keycloak, used by keycloak-server, digest sha256:3f3c5f8e03c614774b4bd9173b88391fefa4153bfc010d8012d59ad825377332
binary archivekeycloak-26.8.1.tar.gz26.8.1Apache-2.0https://github.com/keycloak/keycloak/releases/download/26.8.1/keycloak-26.8.1.tar.gz
OS packagejava-21-openjdk-headlessversion of the configured repositoryGPL-2.0-only WITH Classpath-exception-2.0RHEL family (dnf)
OS packageopenjdk-21-jre-headlessversion of the configured repositoryGPL-2.0-only WITH Classpath-exception-2.0Debian family (apt)

Images are pinned by tag in the descriptor, and by digest when the descriptor declares one (the offline bundle then refuses a pulled image that does not carry it); the digest is recorded in the mirror of the Manager when the offline bundle is imported, and every pull or load is checked against it.

Supported systems and architectures​

MethodOperating systemsArchitectures
binaryRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64, aarch64 (not restricted by the descriptor)
podmanRHEL family (dnf), Debian family (apt), Arch Linux (pacman)x86_64, aarch64 (not restricted by the descriptor)

Certified host systems: RHEL 8/9/10, Rocky Linux 8/9/10, AlmaLinux 8/9/10, Oracle Linux 8/9, CentOS Stream 9/10, Ubuntu 22.04/24.04, Debian 12, Arch Linux (rolling). The host preflight accepts these systems (other releases of a known family give a warning, end of life releases are refused) and the x86_64 and aarch64 architectures.

Prerequisites​

Host​

  • at least 2048 MB of memory (blocking, memory).

Network and ports​

ComponentPort namePortOpened in the host firewall
keycloak-serverhttp8443/tcpyes
keycloak-servermanagement9000/tcpyes
keycloak-serverjgroups7800/tcpyes
keycloak-serverjgroups_fd57800/tcpyes

Services and connections needed​

  • database: postgresql.
  • directory: ldap (optional).
  • entra: oidc (optional).

Details and resolution: see Dependencies.

Installation methods and modes​

MethodDefaultWhat the method uses
binaryyesthe binary archives of the descriptor, unpacked under the service directory
podman-the container images of the descriptor, run by Podman under systemd

Components​

ComponentKindInstallation methodsPorts
Keycloak server (keycloak-server)masterbinary, podman8443/tcp, 9000/tcp, 7800/tcp, 57800/tcp

Single node (standalone) (default)​

One Keycloak node, local cache.

What the mode deploys:

ComponentPlacement
keycloak-servermin 1, max 1

Cluster (cluster)​

Several nodes sharing distributed caches (JGroups, discovery jdbc-ping through the database).

What the mode deploys:

ComponentPlacement
keycloak-servermin 2, recommended 3

Install this service​

The install wizard of the Navin Manager plans, validates and runs the installation; you need the services:install permission on the cluster.

  1. Open the wizard. In Clusters, choose the row action Install services of the target cluster. The wizard opens on its first step, Service.

  2. Choose the service. On the Service step, select Keycloak. The card shows the licence Apache-2.0 and the dependencies the installation needs. Pick the Method among binary, podman (default binary).

  3. Choose the hosts and the mode. On the Hosts step, tick the hosts, then choose the Mode: standalone (default), cluster. Each mode deploys the components listed in Installation methods and modes.

  4. Bind the dependencies. On the Bindings step, choose for each dependency (database, directory, entra) Install with the platform or Use an existing connection; an optional dependency can stay on No binding.

  5. Configure. On the Configure step, review the parameters (see Configuration parameters). Passwords left empty with a generated default are generated and sealed by the Manager.

  6. Review and install. On the Install step the Manager validates the plan and shows the installation order; when it says "The plan is valid. Ready to install.", choose Install. A highly available mode is installed only when its HA checks pass.

  7. Verify. The operation ends when the health checks of every instance pass (see Health checks); the service then shows as running in Services.

Connect an existing service​

Schemeshttps, http
Default port8443
Authenticationrequired
Health checkmanagement_url + /health/ready
Authentication methodFieldsDescription
client_credentialsclient_id, client_secretConfidential client of the realm (for example control-plane): its id and the secret of its Credentials tab.

Official documentation: https://www.keycloak.org/docs/latest/server_admin/index.html#_service_accounts

FieldTypeDefaultDescriptionNotes
Management interface URL (management_url)url-Management interface URL of the existing service.-
Realm (realm)stringnavinRealm used by the platform.-

High availability​

Clusternative (native)
High availabilitynative (native)
Failoverload balancer (load-balancer)
Replicationnative (native)
Quorumnone (none)
Discoverydatabase (database)
Entry pointload balancer (load-balancer)
Official documentationhttps://www.keycloak.org/high-availability/introduction
Peer TLS parametertls_enabled

Prerequisites​

PrerequisiteMust be highly availableModesDescription
databaseyesmodes of level ha or clusterHighly available PostgreSQL holding realms, users and offline sessions.

Topology per mode​

ModesHighest catalog levelDistributionQuorum componentFault domainsDescription
standalonestandalone (standalone)single (single)-1One node with a local cache.
clustercluster (cluster)active-active (active-active)-2Nodes sharing the embedded Infinispan distributed caches, discovered through the database (jdbc-ping).

Notes​

  • The nodes find each other through the database (jdbc-ping): the JGroups port must be open between them.

Configuration parameters​

Network​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
HTTP(S) port (port)port8443-nonoyesPort of the login pages and of the OIDC endpoints (HTTPS when TLS is on, else HTTP).
Management port (management_port)port9000-nonoyesPort of /health and /metrics.
JGroups port (jgroups_port)port7800-nonoyesCluster transport between the nodes (cluster mode).
JGroups failure detection port (jgroups_fd_port)port57800-nonoyesFailure detection port of JGroups (FD_SOCK2, JGroups port plus 50000).
TLS (tls_enabled)booltrue-nonoyesServe HTTPS with a certificate of the manager CA (plain HTTP only behind a TLS proxy).
Public URL (public_url)urlhttps://{{ host.fqdn }}:{{ config.port }}-nononoAddress the browsers and the Control Plane use (hostname of the issuer).

Realm​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Realm (realm)stringenterprise-ai-nononoRealm of the platform (imported from deploy/keycloak at first start).
Import the realm (import_realm)booltrue-nononoImport the enterprise-ai realm at start when it does not exist yet.
Portal URL (portal_url)urlhttps://{{ host.fqdn }}:3000-nononoAddress of the portal, allowed as redirect URI and web origin of the portal client.
Bootstrap admin password (admin_password)passwordgenerated-noyesnoTemporary admin of the master realm, user admin; replace it after the first login.
Initial user password (initial_password)passwordgenerated-noyesnoTemporary password of the imported users (change and TOTP enforced at first login).
Control Plane client secret (control_plane_client_secret)passwordgenerated-noyesnoSecret of the confidential client control-plane, given to the Control Plane through its binding.

Tuning​

ParameterTypeDefaultAllowed valuesRequiredSecretRestartDescription
Java heap (heap)size2gmnonoyesMaximum heap of the JVM. (recommended clamp(round(host.memory_mb * 0.25), 1024, 8192))
Log level (log_level)enumINFODEBUG, INFO, WARN, ERRORnononoRoot log level.

Dependencies​

For each active dependency the Manager takes the first of: the binding chosen in the wizard; a service of the same installation that provides it; a service already installed in the cluster; the only connection of the expected type. Otherwise an optional dependency stays unbound, and a required one is added to the installation in its default mode (the column below names the catalog service added).

BindingProvided byConnection typeEndpointOptionalWhen nothing is boundDescription
databasepostgresqlpostgresqlsqlnopostgresql is added to the installationDatabase of the realms, users and sessions.
directory-ldap-yesstays unbound (optional)Directory of the bank (LDAP or Active Directory) federated in the realm, declared as an LDAP connection of the Manager.
entra-oidc-yesstays unbound (optional)Microsoft Entra ID tenant brokered by the realm (OpenID Connect connection: issuer, client id and secret).

Endpoints​

EndpointSchemeComponentPortPathTLS parameterBinding parametersBinding secretsProvisioning command
httphttpkeycloak-server8443 (port)-tls_enabledissuer, jwks_url, client_idclient_secret-

Client configuration files​

Files rendered for the client configuration download:

  • keycloak.env (client.env.j2)

Commands​

CommandComponentTargetDescription
Export the realm (export_realm)keycloak-serverfirst hostExports the realm to a file under the data directory (users excluded).

Health checks​

Liveness (per instance)​

ComponentCheckDetails
keycloak-serverHTTP {{ 'https' if config.tls_enabled else 'http' }}://{{ host.fqdn }}:{{ config.management_port }}/health/readyExpected 200; 90 retries; interval 2 s; timeout 5 s

Readiness (service check)​

CheckDetails
HTTP {{ config.public_url }}/realms/{{ config.realm }}/.well-known/openid-configurationExpected 200; 10 retries; interval 3 s; timeout 5 s

Preflight checks​

CheckTypeMeaningSeverityComponents
memorymemory_mb {"min": 2048}at least 2048 MB of memoryblockingevery component
port_freeport_free {"param": "port"}port 8443 free on the hostblockingevery component

Uninstall​

Paths removed when the data is purged: {{ paths.data }}, {{ paths.log }}.

  • Administration console: {{ config.public_url }}/admin/
  • OIDC discovery: {{ config.public_url }}/realms/{{ config.realm }}/.well-known/openid-configuration

Upstream documentation​