You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by Adam Hajdul <ad...@gmail.com> on 2026/04/09 16:13:58 UTC
Authentication and other options when joining existing connection
Hello All,
I am writing a custom application based on guacd 1.6.0.
I am parsing guacamole protocol on my own.
In the documentation here
https://guacamole.apache.org/doc/gug/guacamole-protocol.html#joining-an-existing-connection
it is written that
"The rest of the handshake phase for a joining connection is identical.
Just as with a new connection, the restrictions or features which apply to
the joining connection are dictated by the parameter values supplied during
the handshake."
After sending "select" command to join existing session, guacamole returns
parameters same as for original connection, e.g.
"8.username,8.password,5.width,6.height,3.dpi,15.initial-program,11.color-depth"
However I noticed these are not used when provided.
E.g. username and password can be anything, and still connection is joined.
I assume that for joined connections, guacamole sends protocol specific
data as-is, skipping protocol-specific authentication that took part in
initial connection.
Is that correct?
How to distinguish meaningful parameters from not needed?
Is it possible to enforce authentication for users joining existing
connections?
Wouldn't it be better if guacamole indicates only really used parameters in
case of joining handshake?
Thank you in advance