[JIRA] (JENKINS-39234) User identified as Tomcat's unix user id when using Kerberos SSO behind reverse proxy

[dirk.heinri...@recommind.com (JIRA)]

Title: Message Title

Dirk Heinrichs commented on JENKINS-39234   Re: User identified as Tomcat's unix user id when using Kerberos SSO behind reverse proxy Just ran into this and got it solved by using all the "proxy_set_header" directives from this post. Ended up using this (quite simple) config snippet: location / { proxy_pass_request_headers on; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $http_host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $http_host; proxy_set_header X-Forwarded-Server $host; proxy_pass http://127.0.0.1:8080; } My originnal (non-working) version didn't set the "X-Forwarded-*" headers. Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175662.1477386395000.1051.1577722560342%40Atlassian.JIRA.