Dear Guacamole ML,
I'm regularly using the guacamole-auth-json extension to temporary allow
a user to access remote hosts.
When the user requests the access to <connection_A> at <TIMESTAMP_A>, my
API creates the connection using the above extension, and generates an
HTTPS link pointing directly to the newly created connection object, on
Guacamole UI.
=> This works.
The user sometimes requests an access to another host <connection_B>
later on, at <TIMESTAMP_B>, my API generates the link the same way.
=> This also works... except that it also disconnects user from
connection_A, if the user still had a tab open in their browser.
In other words, with this scenario, my user can only access one host at
a time, and that is a problem.
The cause of this disconnection is that the Guacamole JS client sets the
GUAC_AUTH key into the LocalStorage of the browser. So that it can only
make user of one auth key for the whole browser.
As a workaround, I can of course use another browser profile/private
mode or disable LocalStorage globally, use one domain per connection(!),
etc..., but all of this is quite overkill.
Shouldn't this very scenario make use of SessionStorage instead of
LocalStorage?
Or did I misunderstand something else?
(didn't find a GUACAMOLE issue referencing it)
Have a good day,
Toine
#######
{
"username" : "arbitraryUsername",
"expires" : TIMESTAMP_A,
"connections" : {
"connection_A" : {
"protocol" : "rdp",
"parameters" : {...}
},
}
}
{
"username" : "arbitraryUsername",
"expires" : TIMESTAMP_B,
"connections" : {
"connection_B" : {
"protocol" : "rdp",
"parameters" : {...}
},
}
}
######
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
