Password for each data set

[dskyeong]

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]

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 ***@***.***> 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 <#154?email_source=notifications&email_token=AACL4TMW3PWQRGLTTIUGCL3Q2QQXBA5CNFSM4J7HZNGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICUVU3Q>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACL4TP3ZQ43CQDO3TWKJ7LQ2QQXBANCNFSM4J7HZNGA> .

[Gibbsdavidl]

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]

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

[maximilianh]

@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]

@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 matteobrusa/Password-protection-for-static-pages#22 after the <script> line.
generate the sha1 hash string and rename the original index.html as .html
cp index.html from the aforementioned repo to replace the original one. cp the sha1.js to the root of the website as well.

I'll admit that this is quite ugly. But it works for me. The webpage now requires a password and reveals none of the sha1 string in the url.

I will try your solution for apache later as well. But right now I am pretty satisfied by this redirecting solution. ;-p

[maximilianh]

Hey, is this for a submitted manuscript? Should we host the dataset for you, once it's accepted? Or are you building a general single cell website?

…

On Wed, Sep 1, 2021 at 3:30 PM StupidArcher ***@***.***> wrote: @maximilianh <https://github.com/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 matteobrusa/Password-protection-for-static-pages#22 <matteobrusa/Password-protection-for-static-pages#22> after the <script> line. generate the sha1 hash string and rename the original index.html as .html cp index.html from the aforementioned repo to replace the original one. cp the sha1.js to the root of the website as well. I'll admit that this is quite ugly. But it works for me. The webpage now requires a password and reveals none of the sha1 string in the url. I will try your solution for apache later as well. But right now I am pretty satisfied by this redirecting solution. ;-p — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#154 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACL4TMI5LEQVEXSB6Y2RILT7YTJBANCNFSM4J7HZNGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[lijxug]

@maximilianh No, that's just a temporal web browser for my coworkers right now.
This project is not ready to publish yet, but we appreciate your offer and will definitely consider it in the future!

[maximilianh]

I think you're overdoing this. If it's internal-only, you don't need a password at all. I'd just put it onto your webserver, into a subdirectory with the name 38Q1Tb9RhT (see random.org). As long as your webserver does not allow browsing all directories (they usually don't), this will be just fine.

…

On Thu, Sep 9, 2021 at 11:05 AM StupidArcher ***@***.***> wrote: No, that's just a temporal web browser for my coworkers right now. This project is not ready to publish yet, but we appreciate your offer and will definitely consider it in the future! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#154 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACL4TJDBU5CFNRYAH6BDTDUBB2EFANCNFSM4J7HZNGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.