Proxmox and guacamole integration (for real, this time)

[Offf256]

I've done my fair share of googling, but unfortunately pretty few information is available how to integrate PVE (for real) w. guacamole
Sure, there is couple of comprehnesive article how to create LXC or VM and run guacamole within it.
Also, how to run guacamule in docker within above.
BUT... they all stop on "integration" point. How to get a "real web console" -- the one that needs no more than 443/HTTPS and also how ALL newly created VMs get automatically integrated w. guacamole web console. And yep.. I need machine console to be publicly available. Not some service or port... console.
There is one interesting project but unfortunately it is diploma-project and seems to have no active developers/deveopment lately.
https://github.com/osc3b/proxmox-guacamole-client/

My goal is basically a web service where you can create VM (based on template of course) and the access to aforementioned VMs console. All over HTTPS.
Sees unprobable that no one ever did something similar. I can, of course, build it all by myself, but i prefer to use ready-made-components as much as possible.
Any other suggestions similar to aforementioned prject?

 

[LnxBil]

A few years ago I also looked into it, and it boild down to have the authentication and requesting of the websocket in the backend and "just" pass it through to guacamole. In the end I deceided that I don't have time to implement it and just setup users in PVE to do everything directly over PVE. In the beginning it is a little of work to understand the permission and roles in PVE, but it works really great and does what I needed it to do, so I moved on and never looked back.

 

[Offf256]

A few years ago I also looked into it, and it boild down to have the authentication and requesting of the websocket in the backend and "just" pass it through to guacamole. In the end I deceided that I don't have time to implement it and just setup users in PVE to do everything directly over PVE. In the beginning it is a little of work to understand the permission and roles in PVE, but it works really great and does what I needed it to do, so I moved on and never looked back.

Thank you for your reply.
This is also an option (tho it needs "fat" client to installed on user side, but this is acceptable)
Do I understand correctly - toying around with role-permission model one can create user so restricted that after loggigng on PVE the only thing one sees is list of VMs belong to him(her/it) and only course of action available to user is open SPICE console?

 

[LnxBil]

Do I understand correctly - toying around with role-permission model one can create user so restricted that after loggigng on PVE the only thing one sees is list of VMs belong to him(her/it) and only course of action available to user is open SPICE console?

The users sees a little bit more, but it works as suggested. You need to create your own role ConsoleView with priviledges VM.Console and VM.Audit:



and the VM has a permission for a user with that role:



and after the user logged in (switch to Datacenter view) and you see only the VM, cannot change anything, but can use the console: