Repository navigation
Replies: 2 comments
I think there are two existing mechanims for this:
Having a dynamic backchannel per realm would require setting the front end url on the affected realms, so it's not much different than 1. The only practical difference you bring up is not wanting dynamic master realm backchannel requests. |
0 replies
|
Converted to a discussion. There's probably further clarification needed. The configuration you are describing seemingly starts with just a non-url hostname - can you clarify what form your multiple admin urls are taking? If you were setting the keycloak hostname admin url, then you already would have needed to use a full url hostname. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Description
Hello,
Currently
hostname-backchannel-dynamiccan only be configured globally.This is somewhat problematic when you only need dynamic resolution of backchannel URLs for some realms :
In our case we need it to be enabled for all the realms except the master realm (we don't have/want any backchannel requests to the master realm).
By enabling
hostname-backchannel-dynamicglobally, Keycloak requireshostnameto be fixed to a single url.This is problematic as this does not allow to have the Keycloak admin console accessible on multiple browser urls.
Indeed we have a public and an internal url to access the Keycloak admin console.
The public url is managed by our reverse-proxy to filter external IPs that can access the Keycloak admin console.
This was a working use case with Keycloak 22, which is not possible anymore with Keycloak 26.
Discussion
No response
Motivation
No response
Details
No response
All reactions