Carl,
configure the CAS’ Inspektr client info filter as such (in CAS’ web.xml):
<filter>
<filter-name>CAS Client Info Logging Filter</filter-name>
<filter-class>com.github.inspektr.common.web.ClientInfoThreadLocalFilter</filter-class>
<init-param>
<param-name>alternativeIpAddressHeader</param-name>
<param-value>X-Forwarded-For</param-value>
</init-param>
</filter>
Best,
D.
> On Oct 16, 2015, at 9:43 AM, Waldbieser, Carl <waldb...@lafayette.edu> wrote:
>
>
> When placing CAS behind an HTTP proxy, it is possible to include the client
> IP connecting to the proxy in an HTTP header that is passed on to the back
> end CAS service (e.g. X-Forwarded-For).
> Is it possible to configure CAS to log the value of such a header rather than
> the actual client IP (which would be the proxy in this case, and would not be
> terribly useful).
>
> I am interested in knowing how to do this for both CAS 3.5 and 4.x.
>
> My goal is ultimately to log CAS authentication data (successes, failures)
> along with the actual client IP information from a proxied CAS service.
>
> Thanks,
> Carl Waldbieser
> ITS Systems Programmer
> Lafayette College
>
> --
> You are currently subscribed to cas-user@lists.jasig.org as:
> dkopyle...@unicon.net
> To unsubscribe, change settings or access archives, see
> http://www.ja-sig.org/wiki/display/JSG/cas-user
--
You are currently subscribed to cas-user@lists.jasig.org as:
arch...@mail-archive.com
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
