native SP logger enhancement: include applicationId

[Guillaume Rousse]

Hello.

We host our federated applications behind dedicated HTTP 
reverse-proxies, running a single instance of shibboleth SP for a large 
number of different SAML entities (about 30, currently).

For each application, we have an apache virtual host definition:
<VirtualHost *:443>
     ServerName foo.renater.fr
     <Location />
         AuthType shibboleth
         ShibRequestSetting applicationId foo
         Require shibboleth
     </Location>
</VirtualHost>

And the related configuration override defined in Shibboleth SP 
configuration:
<ApplicationOverride id="foo" entityID="https://foo.renater.fr"/>

Whereas it is quite easy to identify which application is concerned by 
shibd logs, because they include entityId or applicationId, that's not 
the case for native logs... Currently, those logs are flooded by such 
kind of content, and I'm unable to identity which application is 
responsible:
INFO Shibboleth.SessionInitiator.SAMLDS [24273] shib_check_user: 
postData property not supplied, form data will not be preserved across SSO

Could mod_shib traces include applicationId for easier correlation ?

Regards.
-- 
Guillaume Rousse
Pôle SSI

Tel: +33 1 53 94 20 45
www.renater.fr

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3637 bytes
Desc: Signature cryptographique S/MIME
URL: <http://shibboleth.net/pipermail/users/attachments/20180418/2dfa447c/attachment.p7s>