guacamole-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Jumper <>
Subject Re: Authentication mechanism.. Was: New user questions...
Date Sat, 03 Mar 2018 23:46:06 GMT
On Sat, Mar 3, 2018 at 1:51 PM, Joachim Lindenberg <>

> Hi all,
> I made a proof of concept and implemented my own authentication extension.
> I am however struggling with
> (1)    Changes of (where I put some settings using a
> prefix hyperv.*) are not picked up until I restart tomcat. I´d appreciate
> if changes would be monitored or picked up at login like is for
> user-mapping.xml. Or am I mislead?
> is cached after the first time it is read.
Extension-specific files, like user-mapping.xml (which is used by a
built-in extension), are governed only by how the extension was written.
The reason that user-mapping.xml is automatically reread upon modification
is because the underlying built-in extension is written to do so. You can
do this for your extension, too, of course - define your own configuration
file which is read from within GUACAMOLE_HOME, and re-read if changed.

(2)    I need a json parser. Looks like there is none exposed by tomcat8 or
> guacamole. I had to copy a json implemention into my jar, which does not
> look like a good solution to me. Is there a way to refer to a standard json
> implementation?

I believe Guacamole bundles Jackson, so you might be able to use that,
however you are indeed expected to bundle your own dependencies. Extensions
are loaded within their own child classloaders with this in mind.

(3)    It is still unclear to me what configuration changes I can/should
> support, and how to best trigger restore of VMs. One approach I am
> experimenting with is to subclass GuacamoleConfiguration and “monitor”
> whether parameters are accessed and then as a side effect trigger restore.
> However the unpleasant aspect is that I´d also have to cache credentials of
> the user then. Any better approach?

Can you clarify what you mean here? What do you mean by "restore" in the
context of VMs, and why are you trying to trigger this as a side effect?
Can you describe what you're trying to achieve at a high level - based on
the overall goal, rather than the specifics of your current implementation?

- Mike

View raw message