Mike, Once again you and your team are awesome! So I have mysql then failover to radius setup for authentication. By leaving mysql 1st and the user trying to authenticate its not going to cause conflicts is it? Do I leave the password blank or is there a tick option or something to let it know that radius will be authenticating them?
Brian From: Mike Jumper [mailto:mike.jum...@guac-dev.org] Sent: Monday, April 16, 2018 10:01 PM To: user@guacamole.apache.org Subject: Re: Radius On Mon, Apr 16, 2018, 17:04 Fertig, Brian <brian.fer...@philips.com<mailto:brian.fer...@philips.com>> wrote: Gents, So after some fooling around I got the radius auth with 2factor and mysql auth working the way I want. Thanks for this project it so far rocks! So couple questions is there a way to have the users cached from radius in the SQL database so I can assign permissions even though they come in via radius? Not "cached", but yes. You will need to create users in the database with the same usernames as the users authenticating via RADIUS. The MySQL auth will provide access to the connections granted to those users when they authenticate via any other installed auth extension, including RADIUS. As well I was testing out an RDP connection and guacadmin is stuck trying to connect to it.. How do I keep him from when he logs in to automatically trying to connect to the RDP session? I would like him to login and hit the admin panel. This is a behavioral quirk that was recently addressed: https://issues.apache.org/jira/browse/GUACAMOLE-508 See also: https://lists.apache.org/thread.html/a884be13ba6d68e3c272203fc07896fb13d5941dc04852733fc7beb4@%3Cuser.guacamole.apache.org%3E You can work around this for the time being by adding a second connection. - Mike ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.
