Description

In old Wildfly based Keycloak distribution, I facing issue while running the keycloak as container behind the nginx proxy while same configuration is working in keycloak-x v17.

I am able to deploy and access the keycloak running in a container by directly using instance IP.

But when i try to access using registered DNS over https configured with help of nginx proxy, after opening main page "Administration Console" is pointing to "https://keycloak:8443/auth/admin/"

Scenario 1: Keycloak-x (v17) in a conatiner ---> VM IP and respective Port --> able to access and login working fine

Scenario 2: Keycloak-x (v17) in a conatiner ---> Nginx Proxy ---> DNS with proper certs --> able to access and login working fine

Scenario 3: Keycloak (v16) in a conatiner ---> VM IP and respective Port --> able to access and login working fine

Scenario 4: Keycloak (v16) in a conatiner ---> Nginx Proxy ---> DNS with proper certs --> able to access main page but login not working as it is pointing to "https://keycloak:8443/auth/admin/"

From my observation in keycloak-x "KC_HOSTNAME" is providing the actual DNS on login.

So, for legacy keycloak is there any similar environment variable available ?

Discussion

No response

Motivation

No response

Details

No response