Resolving the client IP / End user IP
For HTTP Connections, client IP addresses are resolved depending on which HTTP configuration the request comes from. Each connection may have a different way of resolving an end user IP. See all configuration options here.
You may for example configure what header (if any) contains the end user IP, and which syntax it follows (supported syntaxes are
comma separated like X-Forwarded-For and standardized like Forwarded).
If the HTTP configuration does not contain any settings for resolving end user IPs, the global parameter phenixid.auth.client.address is used (read more here).
So you may set a global fallback header to resolve IPs from if your HTTP configuration is missing IP resolve settings. If no such
fallback header is set, the last resort for IP resolving is the socket IP address, which would usually be the IP of a reverse proxy depending on
your environment.
This client IP is used throughout the application for HTTP requests, e.g. in audit logs, in BankID API calls, and more.
In pipes this resolved client IP is available through the request parameter resolvedclientip. Note that this will only
be accessible through HTTP connections, and for example RADIUS connections will not use this system.