Password protection #18

Nexum opened this Issue Dec 12, 2011 · 4 comments


None yet
2 participants

Nexum commented Dec 12, 2011

I would really like to see a simple .htaccess style Authentification so not everyone can use the editor, i could really use this when developing on a foreign machine :)


coreh commented Dec 19, 2011

You're right, that's useful for remote access. I'll add a command line argument that triggers connect's basicAuth middleware.

How important do you think it is to be able to specify the password via a config file? For your use case, is it enough to pass it directly from the command line? Something like:

$ nide --username AzureDiamond --password hunter2

Nexum commented Dec 23, 2011

Hm i think that would be enough for a start, better would be to specify a file where we could set a user and password. i would like to try to implement nide into a cms, something like "activate nide" then get an overlay with nide inside an iframe, now this should be password protected so i can send this information when opening the iframe and no one could intercept, but everyone in my application could use it :)

Nexum commented Dec 23, 2011

When i think about it, command line would really be enough, i can then configure a node script with the username and password and start nide from inside of the script.

coreh added a commit that referenced this issue Dec 29, 2011

Add basic authentication and the ability to specify a host IP.
- Add `--username` and `--password` options for authentication. (Implement feature requested at issue #18)
- Add `--host` option for specifiying a host IP. (Implement feature requested at issue #22)

coreh commented Dec 29, 2011

The latest version on the repository now supports this. I'm going to include it on the next release.

@coreh coreh closed this Dec 29, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment