Hi Nick Just to bookend this. Following your advice, I've (experimentally) removed that screen via: -SecurityTypes None for the Tiger VNC server launch. Of course this is dangerous unless the outer layers, firewall, guacamole password etc. provide some decent protection on the way in.
Thanks Hugh B --------- https://www.hughbarnard.org Twitter:@hughbarnard Mastodon: @[email protected] Book: https://tinyurl.com/2s4hm33b at Housmans and Freedom Bookshop On Monday, 13 May 2024 at 21:51, Nick Couchman <[email protected]> wrote: > On Mon, May 13, 2024 at 2:41 PM Hugh Barnard > <[email protected]> wrote: > >> Hi folks >> >> I now (mis?)understand that noauth isn't in the latest releases 1.5.5 for >> example? This may explain why I couldn't get it working... > > The noauth "authentication" extension was deprecated and removed quite a > while ago. I can't remember exactly when, but it's been years. > >> I'd really like to remove the intermediate (brown background) password >> screen though. It feels as though (I'm using user-mapping.xml) the first >> login screen with user and password is 'enough'. > > The "first" login screen is the Guacamole web application login. The second > (brown - black, maybe) screen is likely the authentication for the remote > connection (VNC, RDP, SSH, etc.). If you want to "bypass" this screen, then > you need to provide the required credentials for the remote connection within > the connection configuration. If you're using user-mapping.xml, this would > involve adding the XML entries for the username and password parameters > (unless it's VNC and only requires a password). > > You can find some examples of this in the user manual: > > https://guacamole.apache.org/doc/gug/configuring-guacamole.html#user-mapping-xml > > -Nick > >>
