Repository navigation
Replies: 4 comments 1 reply
This is expected behavior. If you want to use the master admin console, then you need to login via the master front-end URL - just like any other application that integrates with Keycloak.
See the docs https://www.keycloak.org/docs/latest/server_admin/#the-master-realm on using the individual realm admin consoles rather than the master admin console: "See Dedicated Realm Admin Consoles if you want to disable the master realm and define administrator accounts within any new realm you create. Each realm has its own dedicated Admin Console that you can log into with local accounts." |
|
@shawkins I am not sure dedicated admin console use it right approach here.....
However, as I mentioned, we are using reverse proxy w/ Keycloak
If one if to follow the "Exposed path recommendations" in the proxy docs, then use of dedicated admin consoles is out of question... I was hoping that specifying separate |
|
The most reasonable approach is likely to create ACLs in HAProxy to allow access to the admin console (i.e., anything starting with |
Access to each realm's security consoles is not an issue here - the issue is that If I configure Keycloak with With configuration from my original post,
This means that restricting HAProxy to allowing only makes master admin console unusable even with I think what I have to do is, in addition to above, also add ACL that will allow access to Thanks |
Uh oh!
There was an error while loading. Please reload this page.
Hi
We use Keycloak behind reverse proxy under context root of
/authOur
keycloak.conffile contains appropriate config using docs for reverse proxy and HOSTNAME_V2In our HAProxy (our reverse proxy) we have, as per docs, exposed only
to be available publicly
However, I am noticing that, when logging into Admin Console of the
masterrealm, I am actually being redirected to public URL during login itself...Our goal would be to actually restrict (via proxy) access to only realms we need, and would omit
masterrealm completely.For example:
But this is not working as it then becomes no longer possible to log into Admin console (even though separate Admin URL was specified)
Is this a bug or is my Keycloak configuration incorrect ?
Again, our goal is to not expose
masterrealm publicly at all - is this possible?Thanks
Z..
All reactions