NginX for basic authentication #125
IronOxidizer
started this conversation in
General
Replies: 2 comments 1 reply
-
|
Have you tried the cookie-based auth? The issue is still open (#26) because there's some fancier stuff I want to implement, but logging in, logging out, and authenticating with sessions works fine, and I've been using it for a while. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I just updated the first comment on #26 to reflect current status; hopefully it won't mislead anyone else into thinking auth is totally unimplemented then. Are there docs that need fixing, too? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Edit: There is very little reason to use this method over Moonfire's built-in authentication. Leaving this up for future reference.
Just wanted to make a note that NginX can be used as a basic authentication measure. I can't speak as to how secure it is, but if you're looking for a stop-gap solution, this seems to work. Do note that live view will not work when using basic authentication, hopefully there's an easy fix.
https://docs.nginx.com/nginx/admin-guide/security-controls/configuring-http-basic-authentication/
This can also be used in combination with NginX-served TLS certs for authentication over HTTPS. This along with 443 portforward + free afraid_org subdomain + DDNS is what I'm using as my setup.
My nginx conf is as follows:
Beta Was this translation helpful? Give feedback.
All reactions