Configure the PingDirectory Server to get traffic through a load balancer
and to record the actual client's IP address.
By default, when a PingDirectory Server is sitting
behind an intermediate HTTP server, such as a load balancer, a reverse proxy, or a cache,
it logs incoming requests as originating with the intermediate HTTP server instead of the
client that sent the request.
To record the actual client's IP address to the trace log, enable
X-Forwarded-* handling in both the intermediate HTTP server and
the PingDirectory Server.
Edit the appropriate connection handler object, HTTPS or HTTP, and set
use-forwarded-headers to true.
Note:
When use-forwarded-headers is set to
true, the server uses the client IP address and port
information in the X-Forwarded-* headers instead of the
address and port of the entity that's sending the request, the load balancer.
This client address information shows up in logs, such as in the
from field of the HTTP REQUEST and HTTP RESPONSE
messages.
On the load balancer, configure settings to provide the
X-Forwarded-* information, such as
X-Forwarded-Host:.