<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 7/18/2018 9:33 AM, Tony Ennis wrote:<br>
<blockquote type="cite"
cite="mid:DM5PR18MB23411847B2645C922D8AC00FE2530@DM5PR18MB2341.namprd18.prod.outlook.com"><span
style="color: rgb(33, 33, 33); font-family: wf_segoe-ui_normal,
"Segoe UI", "Segoe WP", Tahoma, Arial,
sans-serif, serif, EmojiFont; font-size: 14.6667px;">>> My
nginx-powered endpoint checks for a Shib cookie and if not</span><br
style="color: rgb(33, 33, 33); font-family: wf_segoe-ui_normal,
"Segoe UI", "Segoe WP", Tahoma, Arial,
sans-serif, serif, EmojiFont; font-size: 14.6667px;">
<span style="color: rgb(33, 33, 33); font-family:
wf_segoe-ui_normal, "Segoe UI", "Segoe WP",
Tahoma, Arial, sans-serif, serif, EmojiFont; font-size:
14.6667px;">>> present in the http request, redirects to
the Shib login.</span></blockquote>
<br>
If you're reverse proxying from httpd to nginx, then no, you won't
get REMOTE_USER set. You'd need to use headers instead of
environment variables (not the default) and pull the particular
value you want.<br>
<br>
It might be possible to have nginx map an incoming header value to
REMOTE_USER, but I don't know much on the nginx side.<br>
<br>
<pre class="moz-signature" cols="72">--
%% Christopher A. Bongaarts %% <a class="moz-txt-link-abbreviated" href="mailto:cab@umn.edu">cab@umn.edu</a> %%
%% OIT - Identity Management %% <a class="moz-txt-link-freetext" href="http://umn.edu/~cab">http://umn.edu/~cab</a> %%
%% University of Minnesota %% +1 (612) 625-1809 %%
</pre>
</body>
</html>