On Thu, Apr 18, 2024 at 10:00 AM Molina de la Iglesia, Manuel <manuel.molina-de-la-igle...@veolia.com.invalid> wrote:
> Hi, > > Similar situation, I have an application that authenticates the user, the > a connection ID and "build" the URL with the token that is where the user > goes. The IP that appears on the log is the address of the server where the > intermediate application is. > > I think this is a different issue - what you're describing is that the IP address that is logged for a user login or connection within Guacamole is the IP address of either the proxy (Nginx, httpd, etc.) or the Guacamole Client system, rather than the actual client (browser) IP address. This is covered in the manual under this section: https://guacamole.apache.org/doc/gug/reverse-proxy.html#setting-up-the-remote-ip-valve I believe the issue that Stephan is describing is that, when the user logs in to Guacamole, and the remote LDAP server that is authenticating the user logs a client IP address, it should log the IP address of the browser (far end client) and not the IP address of the Guacamole Client (tomcat) system. I'm just trying to get clarity from Stephan on whether this is what he's actually trying to do and why. -Nick >
