Repository navigation
Replies: 2 comments 2 replies
|
Moreover, |
The docs are not conveying the full complexity. "Similarly, your reverse proxy might expose Keycloak at a different context path" - is trying to briefly cover the case where the proxy has a context path, but keycloak is not configured for one. The additional assumption is that the proxy is stripping that context path before passing the request to keycloak, so the server in this case does not need to have the relative path set.
It should not be silently ignored. It shouldn't be accepted as a cli option, and if you supply it via another config source you should see a startup error indicating that the build time state has changed. |
Now I understand! Why not explicitly say just that? I have added Many thanks @shawkins ! |
Please open an issue to further clarify the docs. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello, in
https://www.keycloak.org/server/hostname#_defining_specific_parts_of_the_hostname_option
is said that
hostnamefull uri may include a context path (/authin the example). It doesn't mention thehttp-relative-pathparameter, that has to be set accordingly (/auth) for this configuration to work.All reactions