On Tue, Aug 27, 2019 at 12:54 PM Mike Sollanych <[email protected]> wrote:
> >For what it's worth, I did a quick implementation of an authentication > extension that talks to the Consul.IO HTTP API to get service information. > Code repository is here: > > > https://github.com/necouchman/guacamole-auto-consulio > <https://github.com/necouchman/guacamole-auto-consulio> > > > Fantastic effort, Nick, this is incredibly appreciated. I will try it out > within a day or so and give you some feedback. > > Particularly excellent is this: > > > The protocol must be specified in the ServiceMeta node as "protocol", > and any additional connection parameters can be specified in the > ServiceMeta node and will be added to the Guacamole connection. > > This will help make sure it's very configurable and seems idiomatic to the > way people will use Consul, so great call there. > > The only thing that will be problematic here will be the actual > authentication of a VNC session as we use passwords on those, which is > something I'd probably not bake into Consul tags as it's far too easy to > run Consul in a far-too-open sort of state. Any idea if we can simply have > Guacamole prompt for a VNC password on connect? That's good enough for me > for now, considering it's going to be a shared password anyhow. > > Unfortunately, today, no, prompting is not implemented. It's in the works: https://issues.apache.org/jira/browse/GUACAMOLE-221 Also, this version of the extension against the 1.0.0 code probably won't work with connection parameters (e.g. ${GUAC_USERNAME} and ${GUAC_PASSWORD}), either, but I think once we get to 1.1.0 and beyond it'll be able to handle those, as well. -Nick >
