Closed davidjb closed 8 years ago
The answer's not quite on point (https://forum.nginx.org/read.php?2,266934,267415#msg-267415) but it's close enough to say that because there's no common API (aside from the pseudo-API of an nginx config file) between upstreams, we can't achieve this at present.
Feel free to re-comment or re-open if any future someone has any suggestions.
At the moment, in order to achieve the equivalent of
ShibUseEnvironment On
for mod_shib, this module requires manual configuration to pass attributes from Shibboleth to an upstream application. This requires two directives (shib_request_set
and*_param
) for every attribute, which can be tedious to configure, as seen in the sample params config. In addition, a different configuration is needed for each upstream type (egfastcgi_param
,uwsgi_param
,scgi_param
etc).It would be better if the environment parameters could be configured automatically, being enabled via a directive analogous to
ShibUseEnvironment
. Nginx doesn't appear to have a common API across upstream parameters (even though each core upstream's implementation is very similar), so this forum post has been opened to start discussion.