native SP logger enhancement: include applicationId

[Phil Pishioneri]

On 4/19/18 11:07 AM, Guillaume Rousse wrote:
> The current (simple) configuration requires all requests to be
> authenticated, starting a complete authentication process for any
> unauthenticated one, redirecting them to the discovery service:
> <Location />
>     AuthType shibboleth
>     ShibRequestSetting requireSession On
>     ShibRequestSetting applicationId scaner
>     ShibUseHeaders On
>     Require shib-session
> </Location>
>
> One may imagine another configuration that would try to make a
> distinction between requests resulting from human-initiated action
> (GET requests, for instance), and those sort of keep-alive background
> requests. Only unautenticated requests from the first category would
> be redirected to the discovery service, whereas unauthenticated
> requests from the second category would be just replied with a 403 (or
> similar) error status.

If the background URL is distinct from the human ones, then this sounds
similar to the recent discussion (and possible solution) in

http://shibboleth.1660669.n2.nabble.com/Return-401-on-expired-missing-session-tp7638245.html

-Phil