在Nginx / Passenger中托pipe的Ruby / Rails应用程序的头文件中设置环境variables

我为Redmine安装了一个服务器，使用Nginx / Passenger运行。 服务器还托pipeGitlab，并且进展顺利。

我为Redmine提供了一些SSO插件（我发现并安装了这个插件），它需要一个环境variables来填充用户名：这是一个棘手的问题。 到目前为止，我可以分开 ：

• 从X-Forwarded-User头获取用户名
• 自动连接到Redmine传递用户名作为一个常数值
• 自动连接到Redmine传递正确的用户名作为一个常数值testing当前转发的值=>这是丑陋的，需要做每个现有的用户testing

但我不能直接设置用户名与转发的值，它看起来像$ http_x_forwarded_uservariables不被评估…

有一个很好的解决scheme吗？ 我目前的Nginx / Passengerconfiguration：

• 什么时候Windows环境variables是HOMEPATH = \
• 带有SSL nodemanager的Weblogic Managed Server中的环境variables
• Bash构build环境设置
• 在x509下使用REMOTE_USER = SSL_CLIENT_S_DN_CN，在Apache中使用+ FakeBasicAuth。 可能吗？
• 所有用户进程的ulimit等价物？

upstream gitlab-workhorse { server unix:/var/opt/gitlab/gitlab-workhorse/socket fail_timeout=0; } server { listen 0.0.0.0:80; listen [::]:80 ipv6only=on default_server; server_name server.example.com server_tokens off; ## Don't show the nginx version number, a security best practice root /opt/gitlab/embedded/service/gitlab-rails/public; location / { proxy_read_timeout 300; proxy_connect_timeout 300; proxy_redirect off; proxy_http_version 1.1; proxy_set_header Host $http_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://gitlab-workhorse; access_log /var/log/nginx/gitlab_access.log; error_log /var/log/nginx/gitlab_error.log; } location ~ ^/redmine(/.*|$) { alias /opt/redmine/public$1; passenger_base_uri /redmine; passenger_app_root /opt/redmine; passenger_document_root /opt/redmine/public; passenger_enabled on; access_log /var/log/nginx/redmine_access.log; error_log /var/log/nginx/redmine_error.log; # returns "dave", who is the connected user => great ! return 200 $http_x_forwarded_user; # connects on Redmine as Dave => marvelous ! passenger_env_var REMOTE_USER dave; # working but ugly solution if ($http_x_forwarded_user = "dave") { passenger_env_var REMOTE_USER dave; } if ($http_x_forwarded_user = "john") { passenger_env_var REMOTE_USER john; } # ... and so on for every single user having an account... # fails : "user does not exist in database" => $http_x_forwarded_user not being evaluated ?? passenger_env_var REMOTE_USER $http_x_forwarded_user; } }