On Mon, Mar 4, 2019 at 7:49 PM Lev Dubinets wrote:
> To add to that, I'd bet that most serious deployments of guacamole are
> putting it behind nginx or some other proxy and/or load balancer.
>
Yes, though it's mainly guacd that needs the most balancing.
The cookies allow the backend to
To add to that, I'd bet that most serious deployments of guacamole are putting
it behind nginx or some other proxy and/or load balancer. The cookies allow the
backend to control and isolate guacamole sessions or deployments. This is
really useful. For large-scale deployments this has to be a
I've updated the first post to make it an easier and more structured read,
and also to appropriately credit Apache.
-David
--
Sent from:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
On Mon, Mar 4, 2019 at 7:16 PM Lee wrote:
> Mike, thank you for your feedback. I've forwarded that onto my teammates to
> look into. I agree, I'd prefer to not go in a route that is going to be
> constantly against the design of Guacamole, and the links you provide might
> be a great alternative
GianlucaMassimiani wrote
> 1) Install an hypervisor (e.g. KVM) on each server
> 2) Install Guacamole on the servers
> 3) Connect to the cloud system through a web browser, being able to see
> which servers are available
> 4) Through the web browser, select a server and specify the software (for
>
Mike, thank you for your feedback. I've forwarded that onto my teammates to
look into. I agree, I'd prefer to not go in a route that is going to be
constantly against the design of Guacamole, and the links you provide might
be a great alternative I did not see while looking at the
On Mon, Mar 4, 2019 at 2:32 PM Lee wrote:
> Thanks Nick and Mike.
>
> The change ended up being on the front end & connection to the
> authentication module. We were destroying the users cookie if they tried to
> re-connect. With the changes to have that information in local storage,
> that
>
On Mon, Mar 4, 2019 at 3:15 PM Lev Dubinets wrote:
> Hi Lee, I actually have the same/similar issue and started a thread about
> this recently:
> http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/1-0-0-LocalStorage-auth-instead-of-cookies-tp4996.html
> .
>
> Probably best
Hi Lee, I actually have the same/similar issue and started a thread about this
recently:
http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/1-0-0-LocalStorage-auth-instead-of-cookies-tp4996.html.
Probably best to merge my thread into yours.
Nick/Mike, can you elaborate why
Thanks Nick and Mike.
The change ended up being on the front end & connection to the
authentication module. We were destroying the users cookie if they tried to
re-connect. With the changes to have that information in local storage, that
broke our authentication process before it started. I
On Sun, Mar 3, 2019 at 12:40 AM Lev Dubinets wrote:
> Hi,
>
> Prior to 1.0.0 I had a reverse proxy in front of Guacamole that modified
> the GUAC_AUTH cookie paths so that I could have two browser windows open
> with two different Guacamole sessions (one at domain .com/username1 and
> other at
Joachim Lindenberg wrote
> Hi Gianluca,
> For my backup application I wrote a Guacamole extension that in essence
> reflects your steps 4+5. I have two directions of integration: the
> extension
> can enumerate all backups and show them in the Guacamole user interface,
> selecting one starts a
12 matches
Mail list logo
