Our approach to this was to use Guacamole in "slave" mode - we added an agent/daemon that given authentication token, IP, Port, Type of connection would start a console session - no concept of user and no persistence required. The authentication is based on a framework specific to Qstack so it cannot easily be open sourced regretfully.
Agreed Guacamole is heavier since it is doing a lot of the work the client would otherwise be doing (novnc handles all the rendering client side) - but for our purposes it has worked very well. Hope this helps, Sverrir On Wed, May 10, 2017 at 9:04 PM, Syed Ahmed <sah...@cloudops.com> wrote: > Sverrir, > > I had looked at Guacamole before I settled with NoVNC for this proposal. I > found Guacamole to be too heavy to be an integral part of Cloudstack. You > require another database setup and the users have to somehow be matched. > I'd be interested to know more about your approach to this. > > Thanks, > -Syed > > On Tue, May 9, 2017 at 2:23 AM, Erik Weber <terbol...@gmail.com> wrote: > >> On Fri, May 5, 2017 at 6:30 PM, Sverrir Berg <sver...@greenqloud.com> >> wrote: >> > Congratulations with the selection! >> > >> > We at Greenqloud have been using NoVNC as integral part of Qstack until >> > recently. >> >> Why not upstream it? ;-) >> >> > We are now using Apache Guacamole >> > https://guacamole.incubator.apache.org/. >> >> Why not upstream it? ;-) >> >> >> -- >> Erik >> > > -- Sverrir Á. Berg Senior Developer - Research & Development sver...@qstack.com | LI: is.linkedin.com/in/sverrir Tel: (+354) 415 0200 | Website: qstack.com <http://www.qstack.com/> | Twitter: @qstackcloud <https://twitter.com/qstackcloud> [image: qstack_blue_landscape.png]
