In fact web application goes through every Authentication provider, but it does not enter when arrives to Tacacs Authentication Provider (it is previous to MySql), just enter to MySql Authentication provider (which is last in Authentication Providers list).
Any idea how to force to enter into Tacacs Authentication Provider? -Gabriel -----Mensaje original----- De: Gabriel Huerta Araujo Enviado el: lunes, 17 de abril de 2023 09:00 a. m. Para: [email protected] Asunto: RE: Change to the way of authenticating provided by Guacamole Nick How can I make Tacacs authentication be executed? Because as Tacacs and DB password is the same, application goes for DB authentication. -Gabriel -----Mensaje original----- De: Nick Couchman <[email protected]> Enviado el: domingo, 16 de abril de 2023 02:03 p. m. Para: [email protected] Asunto: Re: Change to the way of authenticating provided by Guacamole On Sat, Apr 15, 2023 at 9:17 PM Gabriel Huerta Araujo <[email protected]> wrote: > > I did a test and It does not work > > I put mysql-auto-create-accounts (guacamole properties) with true value. > > In fact Tacacs user is same to DB user, but why when I enter with DB user and > its password as is saved in this repository, I can see Active Sessions? The likely explanation for why this works is because the database module gets evaluated, first, and, if the password is the same, the authentication to Guacamole is done by the database module and *not* by the TACACS module. I'd bet that, once the passwords are the same between DB and TACACS, the Guacamole logins will stop showing up in your TACACS system. -Nick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
