SP transaction.log ClientAddress use XFF?

[Douglas Spooner]

Hi Peter

That's great it can be customised, thanks for the tip!  I will experiment on our test system :-)

Doug

Regards

Douglas Spooner, Senior Systems Analyst
Internet Services Team
Royal Society of Chemistry, Thomas Graham House, 
Science Park, Milton Road, Cambridge CB4 0WF, UK
Direct Tel +44 (0)1223 432334, Fax +44 (0)1223 432133 
www.rsc.org

-----Original Message-----
From: users-bounces at shibboleth.net [mailto:users-bounces at shibboleth.net] On Behalf Of Peter Schober
Sent: 08 November 2013 13:08
To: users at shibboleth.net
Subject: Re: SP transaction.log ClientAddress use XFF?

* Douglas Spooner <spoonerd at rsc.org> [2013-11-08 13:05]:
> I was wondering if it's possible to configure the transaction.log to 
> use the X-Forwarded-For header as all the ClientAddreses that are 
> logged show as our traffic managers private IP.

Not that log specifically but the SP's use of the client's IP address, cf. the "REMOTE_ADDR" content setting:
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPContentSettings

> Am I also right in thinking that transaction.log are all the 
> successfully created/authenticated sessions as I was thinking of using 
> this for some reporting.

Here's what you can get out of in in a recent release:
https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPLogging
You can select and structure that info to your liking, to ease or enable post-procesing.
-peter
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

DISCLAIMER:

This communication (including any attachments) is intended for the use of the addressee only and may contain confidential, privileged or copyright material. It may not be relied upon or disclosed to any other person without the consent of the RSC. If you have received it in error, please contact us immediately. Any advice given by the RSC has been carefully formulated but is necessarily based on the information available, and the RSC cannot be held responsible for accuracy or completeness. In this respect, the RSC owes no duty of care and shall not be liable for any resulting damage or loss. The RSC acknowledges that a disclaimer cannot restrict liability at law for personal injury or death arising through a finding of negligence. The RSC does not warrant that its emails or attachments are Virus-free: Please rely on your own screening. The Royal Society of Chemistry is a charity, registered in England and Wales, number 207890 - Registered office: Thomas Graham House, Science Park, Milton Road, Cambridge CB4 0WF