Hi Nick,
Yes, I’ve got an expires in the JSON, however in this use case the user is likely to click on one link then the other in short succession, opening both connections in seperate tabs. I am assuming this will end up in a race condition if the expires time is short lived but not short enough for it to expire.
Tom
On 5 Jun 2025, at 15:36, Nick Couchman <[email protected]> wrote:
Hello all,
I’ve been testing the JSON auth extension, and successfully created a URL that logs in the user and connects to the link described in the JSON.
However, what I’m trying to achieve is that the link given to the user works for a short period, and any new links generated will take them to a new connection.
Each JSON string has one connection in it to allow guacamole to load it immediately without going to a list of available machines.
For example:
Link 1 - JSON - connection to server 1.
Link 2 - JSON - connection to server 2.
However, Guacamole remembers the user session from the initial link and ignores the connection details in the new link. Is there a way to override this behaviour so that whatever link the user clicks on it will take them to that specific connection?
Are you using the "expires" field in the JSON extension? I'm not sure that this will achieve exactly what you want, but it is a way to make sure that the JSON URLs only work for a certain amount of time. See:
-Nick
|
