Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding access control to endpoints #19

Closed
drvladb opened this issue Jun 12, 2021 · 8 comments
Closed

Adding access control to endpoints #19

drvladb opened this issue Jun 12, 2021 · 8 comments

Comments

@drvladb
Copy link

drvladb commented Jun 12, 2021

I wish to web-desktop-environment in Docker form as a multi tenant development environment but cannot figure out a way to safeguard the endpoints so that only I (and people given access) are able to use it. I already have a setup with vouch proxy but cannot figure out how to integrate it. It would be preferable if there was an option to use domains instead of ports or some kind of password mechanism.

@shmuelhizmi
Copy link
Owner

Hey, I am currently working on a way to secure your desktop via password while exposing only only one public port instead of many like the current implementation.
As for using a domain url instead of a up address, you can actually already do that right now but entering a port will always be required.

@drvladb
Copy link
Author

drvladb commented Jun 15, 2021

Sounds cool, can't wait to see it!

@alexfornuto
Copy link

I'm also interesting in trying this project in a secured way. I'm trying to proxy behind Pomerium, and access it directly from a VM instead of going through web-desktop.run.

Is it possible currently to access the DE without using web-desktop.run?

@shmuelhizmi
Copy link
Owner

@alexfornuto you can run the web interface locally by installing the repo on your computer and following the instructions here, in terms of security note that "web-desktop.run" does not send information to anywhere but your server and can even work offline using web caching!

@alexfornuto
Copy link

@shmuelhizmi is "web-desktop.run" the client or the server in that context? In my ideal environment, nothing would run from my local computer, and I could access the web desktop running on my VM from any device,

@shmuelhizmi
Copy link
Owner

@alexfornuto "web-desktop-environment" is made up of two parts, a server to install on the PC or VM you want to control and a client web app that you can host yourself or access from web-desktop.run , if you want to self host the client you can learn how to do it from my last comment

@alexfornuto
Copy link

Thanks @shmuelhizmi. I'm very new to the concept, but having just set up Guacamole for SSH-over-browser access, I now have a better mental reference point for these concepts.

@shmuelhizmi
Copy link
Owner

hey along side the v2 release everything now should be contained under one end point :)
thanks for opening this issue 👍🏽

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants