ansible-infra/playbooks/files/chaosknoten/configs/keycloak/nginx/id.hamburg.ccc.de.conf

# partly generated 2022-01-08, Mozilla Guideline v5.6, nginx 1.17.7, OpenSSL 1.1.1k, intermediate configuration
# https://ssl-config.mozilla.org/#server=nginx&version=1.17.7&config=intermediate&openssl=1.1.1k&guideline=5.6
# Also see: https://www.keycloak.org/server/reverseproxy
server {
    # Listen on a custom port for the proxy protocol.
    listen 8443 ssl http2 proxy_protocol;
    # Make use of the ngx_http_realip_module to set the $remote_addr and
    # $remote_port to the client address and client port, when using proxy
    # protocol.
    # First set our proxy protocol proxy as trusted.
    set_real_ip_from 172.31.17.140;
    # Then tell the realip_module to get the addreses from the proxy protocol
    # header.
    real_ip_header proxy_protocol;

    server_name id.hamburg.ccc.de;

    ssl_certificate /etc/letsencrypt/live/id.hamburg.ccc.de/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/id.hamburg.ccc.de/privkey.pem;
    # verify chain of trust of OCSP response using Root CA and Intermediate certs
    ssl_trusted_certificate /etc/letsencrypt/live/id.hamburg.ccc.de/chain.pem;

    # HSTS (ngx_http_headers_module is required) (63072000 seconds)
    add_header Strict-Transport-Security "max-age=63072000" always;

    # To not have 502s sometimes when logging through PVE use bigger buffer_sizes.
    # The error seemed to occur after logging in and out and in. Maybe related
    # to Keycloak logout settings, but probably not.
    # See:
    # https://stackoverflow.com/questions/56126864/why-do-i-get-502-when-trying-to-authenticate
    # https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size
    proxy_buffer_size 128k;
    proxy_buffers 8 128k;

    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-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-Port 443;
    # This is https in any case.
    proxy_set_header X-Forwarded-Proto https;
    # Hide the X-Forwarded header.
    proxy_hide_header X-Forwarded;
    # Assume we are the only Reverse Proxy (well using Proxy Protocol, but that
    # is transparent).
    # Also provide "_hidden" for by, since it's not relevant.
    proxy_set_header Forwarded "for=$remote_addr;proto=https;host=$host;by=_hidden";

    # Redirect a user opening any not set location on id.hamburg.ccc.de to the account management page.
    location ^~ / {
        return 307 https://id.hamburg.ccc.de/realms/ccchh/account/;
    }

    location /js/ {
        proxy_pass http://127.0.0.1:8080/js/;
    }

    location /realms/ {
        proxy_pass http://127.0.0.1:8080/realms/;
    }

    location /resources/ {
        proxy_pass http://127.0.0.1:8080/resources/;
    }

    location /robots.txt {
        proxy_pass http://127.0.0.1:8080/robots.txt;
    }
}