guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Amador <>
Subject Alternative to using an iframe?
Date Mon, 29 Aug 2016 19:37:46 GMT
Hello everyone,

This StackOverflow post, answered by Mike Jumper, convinced me that moving
away from using an iframe is the right thing to do.

However, I've gotten a bit stuck on figuring out what I need to do to
replace the iframe we currently embed into webpages for our end users to
have easy access to their RDP sessions. Currently, we're able to use
iframes to point to a (cross-domain) URL that looks something like<guac_
connection_username>&password=<guac_connection_password>. This is
convenient for us because the Guacamole/RDP credentials and connection
information are created asynchronously while our end users' remote desktop
instances are starting up on AWS EC2. We stick this connection information
into the Postgres AWS RDS database that Guacamole uses for authentication,
and then when the end users' are ready to connect to these instances, we
can template the above URL to have the iframe automatically connect to a
view of their remote desktop session when visiting the appropriate URL on
our website.

I would greatly appreciate some guidance on how to reproduce this behavior
using the JavaScript API instead of an iframe. I've tried pointing the
URL in the example JS API code to /tunnel on our guacamole server with no
results. I'm not even sure if the support that I'm looking for in this
default tunnel is built in. Will this involve writing our own tunnel
servlet that consumes some query string parameters passed to it, like the
user's Guacamole credentials? I read all the documentation I could find,
and have been working to solve this problem for a few days now, to no avail.

Thanks for your help,
Eric Amador

View raw message