Hi, This seems to be good use case. Also I am noticing when Guacamole is in Asia and VM in US we are seeing disconnection issues. We are thinking to have multiple guacamole in different regions.
Regards, Umesh -----Original Message----- From: Stefan Bogdan Cimpeanu <[email protected]> Sent: Thursday, March 19, 2020 2:03 AM To: [email protected] Subject: Attributed based routing to a specific guacamole server Hello all, We have this setup where we have multiple jump stations in different countries, and we use guacamole for in browser RDP sessions. It’s going great. We do have a requirement that was brought to our attention just recently, where for some countries, data can not leave the country (the main concern is the Downloads folder to get files in/out of the RDP session). This means we’ll have to deploy “local” guacamole servers to serve only that specific country, and not the entire estate. Did anyone had to do a “routing” to a specific guacamole instance based on a specific attribute? be it at user details, or connection details, or some sort of grouping maybe? The end goal would be that a user, after a login, would only access a specific VM via a specific guacamole server. Is this achievable? Regards, Bogdan --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
