Mike Jumper wrote
> The MySQL and PostgreSQL authentication extensions identify connections
> using their integer IDs from the connection_id column in the
> guacamole_connection table. They don't use the connection_name column to
> identify connections
Correct. That was the issue! I encoded the connections via base64
({$fqdn}\0c\0mysql) and then redirected to the encoded string. Its working
just great. Even hitting back, and attempting the next connection (original
issue of this ticket) also works.
Mike Jumper wrote
> For the sake of anyone happening across this email while searching for
> similar things: beware that this is not a recommended approach. Embedding
> credentials within a URL not good practice.
While true, I am so happy I found the ability to do that after 100's of
links opened in google. Our internal lab houses a good 10,000 servers and
there is no access to the outside world, so we really hate security. In
this day and age its almost more difficult to get around it or turn it off.
Regarding the API, I thought that it wasnt external? We were looking for
some way to make RESTful API calls to manage most of this, when we first
took on the project.
Thank you again for your assistance on this, and your past ticket responses
that helped come up with a working integration for us.
--
View this message in context:
http://apache-guacamole-incubating-users.2363388.n4.nabble.com/Connection-errors-on-no-auth-unless-logout-first-tp93p623.html
Sent from the Apache Guacamole (incubating) - Users mailing list archive at
Nabble.com.
