Shibboleth audit logging - Fails to capture client browser IP (x-forwarded-for) in IdP/Tomcat

Cantor, Scott cantor.2 at osu.edu
Tue Mar 7 11:25:41 EST 2017


On 3/7/17, 10:09 AM, "users on behalf of Petursson, Sigurdur" <users-bounces at shibboleth.net on behalf of spetursson at miami.edu> wrote:

> We followed this documented approach to get the x-forwarded-for IP info into our Shib audit logs:

Leaving aside whether that's reliable (chances are it's not, unless you've proven you can't override the value being set by the load balancer from the client), having done so, you simply need to use the already supplied MDC variable for the client's address, as documented.

-- Scott





More information about the users mailing list