Ok Michael. I will take it on account for future releases.
Thanks a lot for your support. -Gabriel De: Michael Jumper <[email protected]> Enviado el: miércoles, 26 de abril de 2023 11:42 p. m. Para: [email protected] Asunto: Re: Change to the way of authenticating provided by Guacamole On Wed, Apr 26, 2023, 6:30 PM Nick Couchman <[email protected]<mailto:[email protected]>> wrote: On Sat, Apr 22, 2023 at 8:09 PM Gabriel Huerta Araujo <[email protected]<mailto:[email protected]>.invalid> wrote: > > Thanks a lot Michael and Nick for your valuable help. > > > > I found out that I was doing something wrong. The Tacacs authentication > provider jar was made with Guacamole version 0.9.14 and I was doing my tests > with Guacamole version 1.4.0. I got a new version of Guacamole (1.4.0) and > added the Tacacs jar and everything works fine. I think for some reason > Guacamole version I had (1.4.0), had some errors. > > Thanks for posting your solution back, here. We do generally design the components to be as backward-compatible as possible, but that is quite a large difference in versions, and things have changed pretty drastically between those versions, so it isn't shocking that some things would not work. With the version sanity checks built into the extension format, a copy of 1.4.0 will refuse to load extensions for 0.9.14, and will instead log an error noting the incompatibility. Gabriel, if your extension lists the target version as "*", you should change it to the specific version your extension was built against. Future versions of Guacamole will still load it as long as they are compatible, and will safely refuse to load it if not. That (or reading the compatibility notes in the release notes) is your signal to rebuild your extension against the new version, making any changes necessary for it to build. - Mike
