反向代理背后的Keycloak

Question

我在服务器上安装了keycloak standanlone，并尝试通过Nginx在反向代理后面使用它。Keycloak绑定到127.0.0.1

server {
server_name auth.dp.net;
location /auth {
    proxy_pass  http://localhost:8080;
    proxy_http_version 1.1;

        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;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/auth.dp.net/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/auth.dp.net/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 = auth.dp.net) {
    return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
server_name auth.dp.net;
return 404; # managed by Certbot
}

Invalid parameter: redirect_uri

Answer 1

转到您的Keycloak客户端的设置，并将有效重定向Uri更改为*。

有效的重定向URI是Keycloak的一种安全机制，它限制重定向发生的位置。在生产中，它应该尽可能精确，以确保安全连接。