You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by rlljorge September 28, 2024
Hello,
I’m using the self-service-password tool behind a proxy, and I noticed that the audit logs are showing the proxy’s IP address instead of the client’s real IP. Many applications support reading the X-Forwarded-For header in such scenarios to correctly log the client’s original IP.
Would it be possible to add native support for this feature?
For example, in the configuration file (config.inc.php), a new option could be added to enable this functionality, something like:
$use_forwarded_for = true;
And the system could then check if the X-Forwarded-For header exists and use that for logging the client’s IP.
Discussed in #994
Originally posted by rlljorge September 28, 2024
Hello,
I’m using the self-service-password tool behind a proxy, and I noticed that the audit logs are showing the proxy’s IP address instead of the client’s real IP. Many applications support reading the
X-Forwarded-For
header in such scenarios to correctly log the client’s original IP.Would it be possible to add native support for this feature?
For example, in the configuration file (
config.inc.php
), a new option could be added to enable this functionality, something like:And the system could then check if the X-Forwarded-For header exists and use that for logging the client’s IP.
Best Regards,
Rodrigo
The text was updated successfully, but these errors were encountered: