问题:keycloak 无效参数:redirect_uri 在反向代理后面

如何在 Keycloak 前正确配置 NGINX 作为代理?

以医生的身份询问和回答这个问题,因为我现在不得不反复这样做,一段时间后就忘记了细节。

这专门处理 Keycloak 在反向代理之后的情况,例如nginx 和 NGINX 正在终止 SSL 并推送到 Keycloak。这与keycloak Invalid parameter: redirect_uri不同,尽管它会产生相同的错误消息。

解答

关键在于的文档 https://www.keycloak.org/docs/latest/server_installation/index.html#identifying-client-ip-addresses

必须设置proxy-address-forwarding以及各种X-...标头。

如果您使用来自https://hub.docker.com/r/jboss/keycloak/的 Docker 映像,请设置环境。参数-e PROXY_ADDRESS_FORWARDING=true。

server {
  server_name api.domain.com;

  location /auth {
    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-Proto $scheme;

    proxy_pass          http://localhost:8080;
    proxy_read_timeout  90;

 }

  location / {
    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-Proto $scheme;

    proxy_pass          http://localhost:8081;
    proxy_read_timeout  90;
  }



    listen 443 ssl; # managed by Certbot
    ssl_certificate /etc/letsencrypt/live/api.domain.com/fullchain.pem; # managed by Certbot
    ssl_certificate_key /etc/letsencrypt/live/api.domain.com/privkey.pem; # managed by Certbot
    include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
    ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

}
server {
    if ($host = api.domain.com) {
        return 301 https://$host$request_uri;
    } # managed by Certbot


  server_name api.domain.com;
    listen 80;
    return 404; # managed by Certbot
}

如果您使用的是另一个代理,那么重要的部分是正在设置的标头:

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-Proto $scheme;

Apache、ISTIO 和其他人有自己的设置方法。