On Fri, Oct 21, 2016 at 2:56 AM, Rishi <2rushike...@gmail.com> wrote:
> Hi Mike,
>
> I did wrote a separate authentication module inspired from noauth however
> the problem still persists.
> It is the cookie that connects to original console and not new one. If I
> remove cookie and try for new
Hi Mike,
I did wrote a separate authentication module inspired from noauth however
the problem still persists.
It is the cookie that connects to original console and not new one. If I
remove cookie and try for new console, it works fine.
Any ideas how can I force flush cookie and let it go
Thanks Mike for detailed information and saving hours in pursuing wrong
path.
I'd definitely look into custom auth and build something for us.
I'm simply looking for a web callback as authentication mechanism. Let me
know if its already present while I proceed to develop one. And in case I'm
On Tue, Oct 11, 2016 at 3:41 AM, Rishi <2rushike...@gmail.com> wrote:
> Hello All,
>
>
Hello Rishi,
> I'm using guacamole in an automated fashion such that after completing the
> external authentication, a new user-mapping.xml is generated.
>
The intended mechanism for integrating Guacamole
Hello All,
I'm using guacamole in an automated fashion such that after completing the
external authentication, a new user-mapping.xml is generated.
The guacamole authentication in this case works correct however websocket
connection for console happens to the last consoled vm. It is not able to
