Currently we have KeyCloak 15 WildFly based instance deployed in standalone mode on our internal network. Our network team made it available externally with a vanity URL through F5 with a VIP behind that is pointing to the KeyCloak instance as pool member. The instance is SSL secured using certs in JKS format. This works absolutely fine.
However with recent vulnerability in all versions below 18 we have decided to upgrade to KeyCloak 18 Quarkus based instance. I went with simple config and KeyCloak started behaving erratic on externally published URL. Internally it works fine with itās hostname followed by https port URL.
Iām sure Iām missing something thatās causing this issue. My network folks told me that there are redirections happening to internal server URL which is nothing but https followed by serverās internal FQDN with port.
If I put the KeyCloak 15 WildFly instance back everything works just fine with same setup on F5.
Have you tried setting the proxy mode? Depending on whether youāre terminating SSL at the F5 or Keycloak, you either need set it to reencrypt or passthrough.
Open that āblank pageā in the browser again and open browser error/network console - I guess you will see some errors related to wrong hostname/port/protocol there - that should give you a clue what is causing a problem.
Thank you very much. This solution worked. However I had to set the hostname value to externally used vanity URL. And then it started working. But for testing purposes, sometime we isolate our network and F5 and try to access the sites internally on their internal address. When I try to access the site internally using internal address, home page loads and as soon as I click āAdmin Consoleā it throws page not found and a hyperlink. When I click the link, it gets redirected to external URL address and loads the page fine. Iām thinking thatās because the hostname field in the configuration file. Is there any way that we can set the hostname field so that it works both externally and internally!