Hi, Thanks will do as suggested.
Regards, Umesh -----Original Message----- From: Nick Couchman <[email protected]> Sent: Friday, December 27, 2019 7:08 PM To: [email protected] Subject: Re: Multiple Auth provider classes in jar On Fri, Dec 27, 2019 at 5:24 AM Umesh Bhatt <[email protected]> wrote: > Hi, > > I have multiple versions of custom auth providers (say V1 and V2 > classes) in my Java code. On my tomcat restart both (V1 and V2) are > automatically loaded. > Now I want to enable and disable only one using guacamole.properties > file, how to achieve this? > > There's not a built-in way to do this with guacamole.properties. Guacamole Client loads your JAR file and reads the guac-manifest.json file, and loads the authentication provider classes that are specified in that file. This is a rather automatic process, and isn't something that has any options for adjusting within guacamole.properties. There are two possible things you can do to get around this. The first is to split your authentication providers into different JAR files and only load the one(s) you want to use. The second is to create a configuration entry in guacamole.properties for both of your extensions and then use those configuration entries to tell your extensions whether or not they should try to authenticate users. Guacamole Client would still pass authentication control to them in its normal order, but you could basically have the authentication provider silently ignore the authentication requests and carry on if it sees some configuration property set to a certain value. -Nick
