Derek Coleman & Associates Inc logoDerek Coleman & Associates Inc

Home / Support / Keycloak on Ubuntu 24.04 LTS

Keycloak on Ubuntu 24.04 LTS — Support & Quick Start

Keycloak 26 identity and access management (SSO, OIDC, SAML) on Ubuntu 24.04 LTS with a unique per-VM admin password.

Email support Product page Azure Marketplace listing

At a glance

Application ports8080 (Keycloak admin console + realms, HTTP)
Open in browserhttp://<VM-IP>:8080/
Admin credential filesudo cat /opt/keycloak/admin-password
Sign in asdcaadmin-<random> (KC_BOOTSTRAP_ADMIN_USERNAME in the credential file — not `admin`)
Service(s)keycloak
Configuration/etc/default/keycloak (bootstrap admin env, root-only); /opt/keycloak/conf/keycloak.conf (http-port=8080)
Logsjournalctl -u keycloak -f
VersionKeycloak 26.2.5 (dev-file database, pre-built; HTTP on 8080)
PlatformUbuntu 24.04 LTS

Quick start

  1. Open http://<VM-IP>:8080/ in your browser (allow inbound 8080 in the NSG; the in-image ufw already allows it).
  2. Sign in to the admin console with the generated bootstrap username AND password (both in the file below — the username is dcaadmin-<random>, not `admin`), then create a permanent admin and change the password.
  3. Create your first realm, add clients for your applications, and put Keycloak behind HTTPS before production use.

First login / credentials

This image generates its admin credential on the VM at first boot — nothing is pre-set. SSH into the VM with the username + key you chose at deploy, then print the generated credential:

ssh <your-username>@<VM-IP>
sudo cat /opt/keycloak/admin-password

Sign in as dcaadmin-<random> (KC_BOOTSTRAP_ADMIN_USERNAME in the credential file — not `admin`).

  1. Print the credential file: KC_BOOTSTRAP_ADMIN_USERNAME (dcaadmin-xxxxxxxx) and KC_BOOTSTRAP_ADMIN_PASSWORD.
  2. Open http://<VM-IP>:8080/ and sign in to the admin console with that username and password.
  3. Create a permanent admin user in the master realm (Keycloak treats the bootstrap admin as temporary), then delete the file.

The file holds TWO lines: KC_BOOTSTRAP_ADMIN_USERNAME (a per-VM name of the form dcaadmin-xxxxxxxx — the username is NOT `admin`) and KC_BOOTSTRAP_ADMIN_PASSWORD. Keycloak treats this as a temporary bootstrap admin: create a permanent admin user, then delete the file once stored securely.

Still stuck?

Email support@dcassociatesgroup.com (response within 1 business day) or send a message via the contact form. Include the offer name, VM size, region, and any log output — sudo journalctl -u <service> -n 100 usually tells the story.