Václav Muzikář

jFTR, created a [tracker](https://issues.redhat.com/browse/QUARKUS-4431) at Quarkus side.

Using dynamically resolved front- and backchannel (while the two being different URLs) is unsupported with the new Hostname v2 provider which will be the default in Keycloak 25. Please see...

> May have been too quick to close. Since the user explicitly does not want a fixed front-end, this case is still not supported with the new hostname implementation. Not...

@shawkins IMHO #17634 is not possible to do. As I mentioned, having non-static frontend url (or having multiple frontend urls) when accessing Keycloak via backend is not something we can...

> if hostname-strict=false, then the expectation is that any token you obtain has to be used via the same url so the issuer matches? `hostname-strict=false` effectively enables dynamic hostname resolution....

@rmartinc Thank you for your input! > Now this is `--hostname-backchannel-dynamic=true`, right? Almost right. :) `--hostname-strict` is still there with v2. Basically the difference is `--hostname-strict=false` enables dynamic resolution for...

> With the hostname V2 there are more options now. I'd say that with v2 there're actually less options but they should be more clear, especially in terms of use...

CC @keycloak/core

@NilsEngelbach If frontend URL (specified by the `--hostname` option) is not specified and is dynamically resolved, backend is dynamically resolved as well. Keep in mind that when an app accesses...

That would be probably a question for @rmartinc. I believe the reasoning is described in https://github.com/keycloak/keycloak/issues/22191.