[ 
https://issues.apache.org/jira/browse/GUACAMOLE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jumper resolved GUACAMOLE-369.
--------------------------------------
    Resolution: Cannot Reproduce

Tried:
 # Configured connection to create a session recording with 
"$\{GUAC_CLIENT_ADDRESS\}" in the filename
 # Logged in as "guacadmin" from machine with IP address X
 # Connected to that connection
 # Observed session recording was created with IP address X in the name
 # Logged in as "guacadmin" from a different machine with IP address Y
 # Connected to that connection
 # Observed session recording was created with IP address Y in the name

The value for this token is not cached, however it is defined as the IP address 
from which the user authenticated. From [the documentation covering 
"$\{GUAC_CLIENT_ADDFRESS\}"|http://guacamole.apache.org/doc/gug/configuring-guacamole.html#parameter-tokens]:

{quote}
The IPv4 or IPv6 address of the current Guacamole user. This will be the 
address of the client side of the HTTP connection to the Guacamole server at 
the time the current user logged in.
{quote}

If the same user logs in from two different locations, the IP address used 
within each of those sessions will correctly match the address of the machine 
being used in each case. If the user's IP address changes after they 
authenticated, the old address will still be used for the duration of their 
Guacamole session.

> ip address in ${GUAC_CLIENT_ADDRESS} not updated
> ------------------------------------------------
>
>                 Key: GUACAMOLE-369
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-369
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-server, guacd
>    Affects Versions: 0.9.13-incubating
>         Environment: ubuntu server 16.04, nginx 1.10.3, tomcat 7.0.68
>            Reporter: Tjareson Toland
>            Priority: Minor
>
> If a guacamole user logs in from a different ip address, the ip address 
> provided in ${GUAC_CLIENT_ADDRESS} for the new session still contains the 
> address from his/her previous session. 
> nginx and org.apache.catalina.valves.RemoteIpValve are configured accordingly.
> catalina.out is showing the right ip address.
> Looks like that the first ip a user is coming from gets somewhere buffered.
> Restart of tomcat resets that behavior.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to