Part of the problem with NoAuth is that the configuration is cached. This combined with the fact that the webapp inherently expects a user account (and NoAuth provides a placeholder user) means the backend essentially lies to the frontend about the semantics of the situation.
With recent changes to the extension API, there is now a concept of an anonymous user, which lacks the same caching and allows the interface to adjust itself for the semantics of anonymity. The true correct way to approach Guacamole integration is to write an extension which does so, and NoAuth doesn't really fill that space well as a general case solution. IMHO - it's probably time to euthanize NoAuth, reinvestigate/define the high-level need that it's meant to fill, and search for a better approach. - Mike On Mar 16, 2017 12:53, "tek0011" <[email protected]> wrote: > But when you click back, its the exact same thing: > > ctrl-alt-shift -> disconnect: > > > > clicking back: > > > > Identical calls. > > Seems like something isnt working correctly. I can also reproduce this by > actually doing ctl-alt-shift > disconnect. Then attempt a brand new > connection. Same issue. > > I don't get why a second connection fails unless I log out first. Which > makes no sense since its no auth and there shouldnt be a need to log out. > > Anyhow, thanks for confirming. > > > > > -- > View this message in context: http://apache-guacamole- > incubating-users.2363388.n4.nabble.com/Connection-errors- > on-no-auth-unless-logout-first-tp93p578.html > Sent from the Apache Guacamole (incubating) - Users mailing list archive > at Nabble.com. >
