On Tue, Mar 21, 2017 at 10:50 AM, tek0011 <[email protected]> wrote:
> So I moved everything over to mysql, with the same exact issue. > > ... > > We then redirect the user to > http://guac_url.com/guacamole/#/client/ppt-tomcattest. > deploy.lab.beer.town/?username=guacadmin&password=somepassword > > and still get: > > 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 - that's there purely to provide a human-readable description. The URL should be something like: http://guac_url.com/guacamole/#/client/123/?username=guacadmin&password=somepassword Though NoAuth and the built-in XML auth happen to use the name as the connection identifier, the two properties are distinct at the API level. 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. This will work in the short term, but things really should be replaced with a purpose-built extension that actually integrates with the external system (or integrate the Guacamole API directly within that external system). - Mike
