search

maximilianh / cellBrowser

main repo: https://github.com/ucscGenomeBrowser/cellBrowser/ - Python pipeline and Javascript scatter plot library for single-cell datasets, http://cellbrowser.rtfd.org
https://github.com/ucscGenomeBrowser/cellBrowser/
GNU General Public License v3.0
102 stars 40 forks source link

Password for each data set #154

Open dskyeong opened 4 years ago

dskyeong commented 4 years ago

Hi, I've installed cell browser 0.7.1. Before releasing data, we need to keep it in personal. Please, let me know how I can set the authority for each data set. Thank you

maximilianh commented 4 years ago

There is no password right now built into it... the reason is that it's hard to limit access from Javascript...

However, because the cell browser is so small, you could simply create a separate cell browser per each project / user. Then, you could put them into different subdirectories of your http server, and have a username/password for each directory. Would that work for you?

Maybe if you explain your setup a little, I can try to find something more customized. Do you have one browser per "customer" ? Are you a core unit? What is your existing storage solution ? How did you handle this problem until now?

thanks! Max

On Thu, Dec 26, 2019 at 4:33 AM dskyeong notifications@github.com wrote:

Hi, I've installed cell browser 0.7.1. Before releasing data, we need to keep it in personal. Please, let me know how I can set the authority for each data set. Thank you

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/maximilianh/cellBrowser/issues/154?email_source=notifications&email_token=AACL4TMW3PWQRGLTTIUGCL3Q2QQXBA5CNFSM4J7HZNGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICUVU3Q, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACL4TP3ZQ43CQDO3TWKJ7LQ2QQXBANCNFSM4J7HZNGA .

Gibbsdavidl commented 4 years ago

I found a partial solution for this: https://github.com/matteobrusa/Password-protection-for-static-pages

Essentially, a password is used to create a long hash, which is then used as a directory name... you create that directory (with the hash as name) and you pop the index.html (and other files) into that hashed directory. works well.

lijxug commented 2 years ago

Waiting for a secured access to the website, too. I followed what Gibbsdavidl recommended. The web page didn't redirect, wierd.

maximilianh commented 2 years ago

@lijxug can you explain what you are trying to do? In principle, if you want a protected URL to send to your users, you can simply create a URL that is very hard to guess. That should be sufficient. The solution by @Gibbsdavidl is not a real password, it just redirects, so if you send around URLs, you don't need the URL.

Also, you can simply activate normal htaccess passwords in your webserver: https://www.digitalocean.com/community/tutorials/how-to-set-up-password-authentication-with-apache-on-ubuntu-14-04

lijxug commented 2 years ago

@maximilianh Yes, that's a partial solution. I've made some changes to that index.html and eventually made it work.

Basically, I have constructed a webpage using your browser. Then I want to send the link directed to the browser only for my coworkers. So I need a password to protect this data set.

Here is what I did: clone the https://github.com/ulfaslak/Password-protection-for-static-pages repo because he fixed the sha1 loading problem. hosted the server with cdBuild open the original index.html, insert the codes suggested by https://github.com/matteobrusa/Password-protection-for-static-pages/issues/22 after the Githubissues.

  • Githubissues is a development platform for aggregating issues.