On Tue, Nov 17, 2020 at 11:08 PM mark P <[email protected]> wrote:
> Thanks. Is there any official API documentation. > Tons: http://guacamole.apache.org/api-documentation/ > For .e.g consider the following flow : a) I hit an API and get an access > token b) Using this access token, I dynamically generate a URL which can be > returned to the client. c) 1000s of users are able to simultaneously use > such end points to access various different virtual machines. > https://github.com/glyptodon/guacamole-auth-json provides this in swiss army knife fashion. Or you could write your own extension which authenticates users and routes connections however you need. BUT: I really don't think you need to do all that. You mentioned earlier that you don't wish to share Guacamole credentials with your research assistants ... but why? The system is intended to be multi-user, with the administrator dictating exactly what each user can access. Unless you're trying to tightly integrate Guacamole into some other existing product, perhaps a product of your own, there's no need to try to create your own authentication system and your own connection authorization system. This is already what Guacamole provides and one of its major benefits. You wouldn't generate some single set of administrator-level credentials and share it with everyone. You would create user accounts that correspond to each student and grant those users access to only what they need. The experience from their perspective would be they go to the URL of your Guacamole server, log in with their credentials, and poof - access to their machines and *only* their machines. Michael Jumper CEO, Lead Developer Glyptodon Inc <https://enterprise.glyptodon.com/>.
