keycloak/keycloak

Attempting to rename Master realm sends user to nonexistent realm

Open

#45.641 aberto em 21 de jan. de 2026

Ver no GitHub
 (3 comments) (2 reactions) (0 assignees)Java (34.398 stars) (8.346 forks)batch import
area/admin/uihelp wantedkind/bugpriority/lowstatus/auto-bumpstatus/auto-expireteam/cloud-native

Description

Before reporting an issue

  • I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

admin/ui

Describe the bug

On latest 26.5.1 keycloak, renaming Master realm fails with "cannot rename master realm" popup error and the admin is sent to a url that doesn't get created. Returning back puts the admin back in the master realm.

I'm aware of #34540, and I think this is a regression cause it exhibits extremely similar behavior.

Version

26.5.1

Regression

  • The issue is a regression

Expected behavior

Master realm gets renamed

Actual behavior

Keycloak ui attempts to rename master realm, fails, gets stuck. realm never gets renamed.

How to Reproduce?

Attempt to rename the master realm at /admin/master/console/#/master/realm-settings

Anything else?

Here's docker compose file that I used.

version: '3.8'

services:
  keycloak:
    image: quay.io/keycloak/keycloak:latest
    restart: always
    command: start
    ports:
      - "8080:8080"
    environment:
      KC_HOSTNAME: https://sso.base48.cz  # Replace with your actual domain
      KC_PROXY: edge
      KC_HTTP_ENABLED: true
      KC_PROXY_ADDRESS_FORWARDING: "true"
      KC_HOSTNAME_STRICT: "false"
#      KC_HTTP_ENABLED: "true"
      KC_DB: postgres
      KC_DB_USERNAME: keycloakuser
      KC_DB_PASSWORD: censored
      KC_DB_URL_HOST: db
      KC_DB_URL_PORT: 5432
      KC_DB_URL_DATABASE: keycloakdb
      KC_BOOTSTRAP_ADMIN_USERNAME: admin
      KC_BOOTSTRAP_ADMIN_PASSWORD: censored
    depends_on:
      - db
    volumes:
      - /root/keycloak:/opt/keycloak/data
      - /root/keycloak-ldap-posixaccount/target/ldap-posixaccount-1.1.3.jar:/opt/keycloak/providers/ldap-posixaccount-1.1.3.jar
  db:
    image: postgres:17.1-bullseye
    restart: always
    environment:
      POSTGRES_USER: keycloakuser
      POSTGRES_DB: keycloakdb
      POSTGRES_PASSWORD: censored
    volumes:
      - /root/keycloak-db:/var/lib/postgresql/data

thanks -v (vcherkas@redhat.com)

Guia do colaborador

Pilha de tecnologia
javareactjavascript
Domain
frontendbackendauthentication
Tipo Issue
bug
DifficultyDificuldade de implementação estimada para um novo contribuidor, de 1 para alterações muito pequenas a 5 para trabalho de nível especializado.
3
Tempo estimadoUm intervalo de tempo aproximado para um colaborador experiente investigar, implementar, testar e preparar um pull request.
1-2 days
Status da atividadeQuão disponível o issue aparece agora: novo, ativo, obsoleto, bloqueado ou aguardando entrada do mantenedor.
fresh
ClarityCom que clareza o issue explica a mudança esperada, os critérios de aceitação e a próxima etapa.
clear
Prerequisites
JavaReactKeycloak
Simpatia para novatosUma pontuação de 1 a 100 que estima o quão acessível este issue é para colaboradores iniciantes.
50
Direção de pesquisa
Investigate the realm renaming logic in the admin UI. Look at the realm settings page (likely at `admin/ui/src/realm settings/RealmSettingsPage.tsx` or similar). Check how the URL is updated after renaming. Also check the backend endpoint for renaming realms (likely in `services/src/main/java/org/keycloak/services/resources/admin/RealmAdminResource.java`). Compare the behavior with the referenced issue #34540 to identify the regression. The error occurs when navigating to a non existent realm after the rename attempt fails.