On Thu, Oct 19, 2017 at 1:36 PM, Colin McGuigan <
colin_guacam...@walkingshadows.org> wrote:

> Update: Without changing any configuration (only working on my extension),
> this problem resolved itself and I now see the websocket tunnel in use.
>
> I have no idea what caused it to change, other than the possibility of
> tomcat restarts.
>
>
Colin,
I did notice something in the following line:

> GET
ws://<Computer>:8080/guacamole/websocket-tunnel?token=
943D0910D316FE59C5C110AD800DFF7FBDFD7529000C1D7503719FD9828D
B69B&GUAC_DATA_SOURCE=saml&GUAC_ID=<Computer>&GUAC_TYPE=
c&GUAC_WIDTH=948&GUAC_HEIGHT=998&GUAC_DPI=120&GUAC_AUDIO=
audio%2FL8&GUAC_AUDIO=audio%2FL16&GUAC_IMAGE=image%2Fjpeg&
GUAC_IMAGE=image%2Fpng&GUAC_IMAGE=image%2Fwebp

The GUAC_DATA_SOURCE=saml is a bit interesting.  I'm guessing that your
SAML extension is only doing authentication, it's not providing any
computer data, correct?  If so, this line indicates the issue, that it
is/was trying to retrieve the connection from the SAML data source, when it
is actually in another data source.  Perhaps the change you made caused it
to correct this parameter??

-Nick

Reply via email to