We are unable to log user ip address in smaccess log in our non-prod environment. The ip captured in REMOTE_ADDR is the LB ip instead of user ip which is being audited as sm_client ip in smaccess logs currently.
However we have X-forwarded-for and Client-ip headers populated correct IP address for user being authenticated.
Is there any way we can force agent to use either of X-forwarded-for or Client-ip to be used while auditing.
Release : 12.52
Component : SITEMINDER -WEB AGENT FOR APACHE
Setting the ACO parameter CustomIPHeader to X-forwarded-for should solve this.
You should not need to change ProxyDefinition and/or RequireClientIP just to include the X-forwarded-for in smaccess.log. Just set CustomIPHeader.