unable to capture eppn information from SAML2/POST at SP

[Peter Schober]

* Brent Putman <putmanb at georgetown.edu> [2018-06-11 23:47]:
> >  nor whether that value was propagated to the REMOTE_USER variable
> (which I suspect didn't happen since I am still not getting the
> expected response in my application)....
> 
> To check REMOTE_USER or any other variable, just use a simple CGI
> script which prints the environment variables.

FYI, Apache httpd logs the value of REMOTE_USER with every line in its
access log. No CGI required.

I haven't yet seen that the OP changed the internal id of the
attribute to something other than "eppn" or alternatively changed the
default attribute-policy.xml: As I've explained in detail what is
being sent here is NOT eppn, so the built-in checks from the SP will
reject that.
Unless either the id is changed in the attribute-map.xml (and again in
the REMOTE_USER precedence list) or the attribute-policy.xml is
changed for "eppn" from the ScopiingRule reference to permitAny.

-peter