Keycloak

Open-source Identity and Access Management (IAM) platform. Provides authentication, authorization, SSO, and identity federation for your applications.

Version:

26.5.3

back to Marketplace

VM Requisites

Resource Minimum
CPU 2 vCPU
RAM 4 GB
Disk 40 GB
Operating System Ubuntu 22.04 / 24.04

Access Port

Port Protocol Usage
80/443 HTTP/HTTPS Administration console and authentication endpoints

How To Access

With SSL enabled (recommended)

https://<IP-CON-GUIONES>.sslip.io/

Example: if your VM has the IP address 200.25.101.125:

https://200-25-101-125.sslip.io/

Admin console

Add /admin/ to the end of your URL:

https://<IP-CON-GUIONES>.sslip.io/

Field Value
User admin (or the value of KEYCLOAK_ADMIN USER)
Password The one configured in KEYCLOAK_ADMIN_PASSWORD or look for it in the deployment outputs

Verify that Keycloak is active

# View the Keycloak pod
`kubectl get pods -A | grep keycloak`

# View the installation log
`tail -f /var/log/cuemby/bootstrap.log`

# Check the health endpoint
`curl http://<VM_IP>:30808/health/ready`

Expected output:

{"status": "UP"}

Expected pod output:

NAME                         READY   STATUS    RESTARTS
keycloak-xxxxxxxxx-xxxxx     1/1     Running   0        ← Running ✓

ℹ️ Keycloak may take ~3–5 minutes to become available after the pod is in Running, as it initializes the database on the first boot.

Configuration Parameters

Parameter Default Description
KEYCLOAK_ADMIN_PASSWORD ⚠️ auto-generated Console administrator user password.
KEYCLOAK_DB_PASSWORD ⚠️ auto-generated Internal PostgreSQL database password.
KEYCLOAK_ADMIN_USER admin Administrator username.
KEYCLOAK_DB_DATA_SIZE 10Gi Persistent volume size for PostgreSQL.
KEYCLOAK_DATA_SIZE 10Gi Persistent volume size for Keycloak data.
KEYCLOAK_SSL_ENABLED true Enable HTTPS with automatic certificate via sslip.io.
KEYCLOAK_HOSTNAME auto (sslip.io) Custom hostname. If left blank, the URL generated by Cuemby will be used.

First Steps (quick start)

  1. Open <URL>/admin/ and log in with your credentials.
  2. Create a new Realm from the top left dropdown menu → Create Realm. The master realm is only for Keycloak administration, not for your apps.
  3. Within the new realm, create a Client for your application from Clients → Create client.
  4. Create users from Users → Add user or configure an external identity provider from Identity Providers.

💡 Tip: Your realm's OIDC endpoints are available at:

https://<IP-CON-GUIONES>.sslip.io/realms/<nombre-realm>/.well-known/openid-configuration

Use them to configure authentication in your applications.

Quick Troubleshooting

Problem Probable cause Solution
Console not loading Keycloak initializing DB Wait ~5 min and verify with curl http://:30808/health/ready.
Invalid username or password Incorrect credentials Check the deployment outputs in the Cuemby portal.
Redirect URI mismatch Client misconfigured Verify the client's Valid Redirect URIs in the administration console.
HTTPS required in realm Keycloak forces SSL Adjust Realm Settings → General → Require SSL to none for development environments.
Pod in CrashLoopBackOff PostgreSQL not yet ready Wait a few minutes; Keycloak requires the DB to be available before starting.

Cuemby Cloud

IaaS

About Cuemby Cloud

Cuemby Cloud is enterprise-grade cloud infrastructure managed from a single console, built for stronger security, predictable operations, and easy scaling across regions.

Datacenters regions available in Colombia, Ecuador, and Chile

Backed by Tier III / Tier IV data center locations

Zero Network Ingress and Egress Fees

24/7 local expert support

Ready to Modernize Your Enterprise?

Future challenges demand future-ready solutions.
Let’s get started!

© Copyright | Cuemby® 2025