Precisely 404 is on
"/auth/admin/realms/b1a5a9f6-5f85-489f-8656-25e5307088be/groups/count?top=true",
it should be "/auth/admin/realms/test/groups/count?top=true".
I am still confused if it is a js problem or not.
2017-12-14 12:25 GMT+01:00 Jean-François HEROUARD <
jfherouard.almerys(a)gmail.com>:
Hi,
On an instance of Keycloak I have strange errors when browsing some realms
(Http 404 on some requests). After some invetigation, the root problem
seems to be in realm database table :
keycloak=# select id, name from realm;
id | name
--------------------------------------+-----------
master | master
5433f7c8-7420-428c-82bc-d96a76da1afe | demorealm
b1a5a9f6-5f85-489f-8656-25e5307088be | test
016cc42d-8f46-4007-8054-e8bd7a923fa5 | testrealm
test2 | test2
For example the groups REST resource expects a name in URL context, but
Angular admin GUI use the realm Id and so get a 404.
Realms were created from Keycloak v3.1.0 until last v3.4.1. Is there some
data migration to do manually (or has previously failed ?). Or is the
groups REST resource expecting the wrong parameter ?
Thanks.