shib SP 2.5.3 and apache 2.4 AccesControl require session

[Peter Schober]

* Jehan Procaccia <jehan.procaccia at tem-tsp.eu> [2018-01-26 16:10]:
> On my old server with shib SP 2.4.3 and apache 2.2.16-6
> [...]
> Now on my new server with shibboleth 2.5.3  and apache 2.4.18

Now why would you build a /new/ server with an /obsolete/ Shib SP to
begin with? (And with no way forward, probably?)

> but my perl script that returns shib vars , keeps showing REMOTE_USER empty,

JFYI, there's no need for such scripts, and there hasn't been one in
many years. You'll see REMOTE_USER in httpd's access log (lines that
do not have " - - " will have the REMOTE_USER in there), you'll see
successfully processed attributes in the SP's transaction.log and at
the /Shibboleth.sso/Session handler, and skipped (e.g. unmapped)
attributes in the SP's shibd.log.

The rest I can't explain either, obviously. Though statements like the
following: 

* Jehan Procaccia <jehan.procaccia at tem-tsp.eu> [2018-01-26 18:14]:
> I want users accessing my location /shibwayf/shibtest.pl to be required to
> login in order to get a REMOTE_USER = eppn
> it works fine on my old server with
> <Location /shibwayf>
>  AuthType shibboleth
>  ShibRequestSetting requireSession 0
>  require shibboleth
> </Location>

simply mean you'll have to have more/other configuration active
elsewhere, as no version of the SP would require sessions with that
configuration alone.

-peter