Keycloak admin console infinite loop

1

Need urgent Help
I have a keycloak docker container. I did nginx proxy configuration for keycloak. When i try to login to admin console, it keeps going in infinite loop. below is the detail:

docker compose:
version: ‘3.9’
services:
jboss-keycloak-server:
image: jboss/keycloak
container_name: jboss-keycloak-server
expose:
- 8081
environment:
KEYCLOAK_USER: epadmin
KEYCLOAK_PASSWORD: admin
KEYCLOAK_IMPORT: /tmp/import.json
DB_VENDOR: postgres
DB_SCHEMA: public
DB_DATABASE: postgres
DB_USER: postgres
DB_PASSWORD: password
DB_ADDR: identity-db
DB_PORT: 9000
ACCOUNT_SID: $ACCOUNT_SID
AUTH_TOKEN: $AUTH_TOKEN
TRIAL_NUMBER: $TRIAL_NUMBER
KEYCLOAK_SMS_AUTHENTICATOR: $KEYCLOAK_SMS_AUTHENTICATOR
KEYCLOAK_SMS_AUTHENTICATOR_ID: $KEYCLOAK_SMS_AUTHENTICATOR_ID
KEYCLOAK_FRONTEND_URL: https:///auth/
KC_PROXY_ADDRESS_FORWARDING: “true”
KC_HOSTNAME_STRICT: “false”
KC_TRANSACTION_XA_ENABLED: “false”
KC_HOSTNAME_STRICT_HTTPS: “false”
#KC_HTTP_RELATIVE_PATH: “/auth”
KC_PROXY: edge
#PROXY_ADDRESS_FORWARDING: passthrough
ports:
- 8081:8080
volumes:
# - ./deployments:/opt/jboss/keycloak/standalone/deployments
- ./imports/import-realm.json:/tmp/import.json

nginx configuraiton:
server {
listen 8084;
listen [::]:8084;

    server_name <domain-name>;

    location / {
      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection 'upgrade';
      #proxy_set_header Host $host;
      #proxy_set_header X-Forwarded-For $remote_addr;
      #proxy_set_header  X-Real-IP  $remote_addr;
      proxy_cache_bypass $http_upgrade;
      proxy_set_header X-Forwarded-Proto $scheme;
      add_header Access-Control-Allow-Origin *;
      proxy_pass http://keycloak:8081/;
      proxy_ssl_verify    off;
      proxy_set_header    Host                $host;
      proxy_set_header    X-Real-IP           $remote_addr;
      proxy_set_header    X-Forwarded-For     $proxy_add_x_forwarded_for;
      proxy_set_header    X-Forwarded-Host    $host;
      proxy_set_header    X-Forwarded-Server  $host;
      proxy_set_header    X-Forwarded-Port    $server_port;

}
}

keycloak version
bash-4.4$ ./standalone.sh --version

JBoss Bootstrap Environment

JBOSS_HOME: /opt/jboss/keycloak

JAVA: java

JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true --add-exports=java.desktop/sun.awt=ALL-UNNAMED --add-exports=java.naming/com.sun.jndi.ldap=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.base/java.lang.reflect=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.security=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.management/javax.management=ALL-UNNAMED --add-opens=java.naming/javax.naming=ALL-UNNAMED

=========================================================================

12:34:31,758 INFO [org.jboss.modules] (main) JBoss Modules version 2.0.0.Final
Keycloak 16.1.1 (WildFly Core 18.0.4.Final)

2

You are using a very old KC version (16) with a wild mixture of old an new environment variables as configuration. Do yourself a favor and update to the most recent version, adjust your configuration to use the proper variables (it’s all in the docs!!!) and try again.
If it still fails, there are already a number of threads here in the forum which might help you.

3

Thanks for your time, if you see the below command, we dont give any version, the available version comes to us as 16

image: jboss/keycloak

if we try any new version, it does not work.

please let us know how to get the new version in docker compose

4

I have updated to 20.0.1, now getting below error
index.0cb2e516.js:90 Refused to frame ‘http://domain-name/’ because it violates the following Content Security Policy directive: “frame-src ‘self’”.

in browser console.