Re: Guacamole Client API
On Fri, Apr 24, 2020 at 10:18 AM netnut wrote: > Reviving an old-ish thread- I need to take users directly to the "desktop" > screen since I don't want to assign my users guacamole user accounts. So > which of the following approaches would work: > > User's browser -> Guacamole Client (tomcat) -> guacd (in this case the user > is presented with the login screen which I don't want) > One way around this is to use some sort of SSO installation that bypasses authentication for users already authenticated elsewhere. But, please read this: http://guacamole.apache.org/faq/#disable-auth Currently Guacamole supports CAS, OpenID Connect, and Header SSO modules, with SAML support in progress. > or > User's browser (custom app using guacamole-js) -> guacd > > If you truly do not want the AAA features of the full Guacamole client, then you should write your own Guacamole application that integrates into some other application that is already providing you with those features. -Nick
Re: Guacamole Client API
Reviving an old-ish thread- I need to take users directly to the "desktop" screen since I don't want to assign my users guacamole user accounts. So which of the following approaches would work: User's browser -> Guacamole Client (tomcat) -> guacd (in this case the user is presented with the login screen which I don't want) or User's browser (custom app using guacamole-js) -> guacd vnick wrote > On Tue, Feb 12, 2019 at 1:11 PM sciUser > shulbert@ > > wrote: > >> Do I have to run the Guacamole client API from the Guacamole server >> itself >> or >> can I call it from another server say hosting lab guides? >> >> > I'm not entirely sure which component you're referring to, but, in > general: > - Guacamole Client (the portion that runs in Tomcat) can be separately > from > guacd - the two do not have to run on the same system. If you run them on > different servers you have to make sure that you configure the Guacamole > Client side to point to the correct Guacamole Server (guacd) instance. > - The portion that access the API actually generally runs on the browser. > The HTML and JS content is, by default, hosted in the same Tomcat > container > as the rest of the Guacamole Client (Java classes, etc.), but this doesn't > have to be the case - you can separate them onto different sources. The > issue you'll have is that you'll have to reconfigure the JS to point to > the > correct place for the API, rather than just defaulting to the same host > from which it is running. > - You can also write custom code to make REST calls to the API endpoints > outside of the normal Guacamole WebApp - it's a standard REST API, and can > be accessed by any code/client that can be configured to make the calls. > > Regards, > Nick -- Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/ - To unsubscribe, e-mail: user-unsubscr...@guacamole.apache.org For additional commands, e-mail: user-h...@guacamole.apache.org
Re: Guacamole Client API
On Tue, Feb 12, 2019 at 1:11 PM sciUser wrote: > Do I have to run the Guacamole client API from the Guacamole server itself > or > can I call it from another server say hosting lab guides? > > I'm not entirely sure which component you're referring to, but, in general: - Guacamole Client (the portion that runs in Tomcat) can be separately from guacd - the two do not have to run on the same system. If you run them on different servers you have to make sure that you configure the Guacamole Client side to point to the correct Guacamole Server (guacd) instance. - The portion that access the API actually generally runs on the browser. The HTML and JS content is, by default, hosted in the same Tomcat container as the rest of the Guacamole Client (Java classes, etc.), but this doesn't have to be the case - you can separate them onto different sources. The issue you'll have is that you'll have to reconfigure the JS to point to the correct place for the API, rather than just defaulting to the same host from which it is running. - You can also write custom code to make REST calls to the API endpoints outside of the normal Guacamole WebApp - it's a standard REST API, and can be accessed by any code/client that can be configured to make the calls. Regards, Nick