-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Web UI - Authentification #40
Comments
Hi @jygastaud Not at the moment - you could proxy it with nginx to add authentication there instead I'll have a look at adding support for it - shouldn't be too difficult. |
👍 I'd love to have the option to require basic auth as well. |
I've added support for HTTP auth, haven't done a new binary release yet though. Let me know what you think - not really sure how well it'll work, bcrypting a password so often will probably be too slow. I'll probably switch to using cookies and api tokens to speed it up when I have a chance! |
If someone's looking for ldap login, I haven't tried yet, but nginx-auth-ldap may be useful here if someone tries to proxy with nginx for auth. |
MailHog -auth-file=docs/example-auth |
This is definitely working now, I imagine this issue can be closed Example command: |
Thanks, glad it's working 👍 I'll keep the issue open for now as a reminder to make password handling less bcrypt-crazy |
Nice! |
@klokie : Basically you will need to override the entry-point that is used as default command by the docker container. In docker compose , something like:
or on the command line just add "--entrypoint MailHog -auth-file=/data/mailhog/auth.file" to you docker run command. |
@fredleger ,
fails with this error:
Any idea? |
Maybe a typo on your side with docker command line? Details about authentification can be found here: The file should be inside docker. I suppose it's easier using docker-compose here, but I do get the same result as you with your command. More details on docker run documentation I was able to make a local MailHog install work this way: go get github.com/mailhog/MailHog
echo "bob:$(MailHog bcrypt bob)" > auth.file
cat auth.file
bob:$2a$04$UIjxgUHqHWL4o5KVrF9AC.sbVxmXSOVMGhyz66Khx5ZFh2BdKnYKO
MailHog --auth-file=./auth.file docker solution🎉 I managed to get it working like this (without
Output from the container's logs:
|
I guess there is something with the dashes here. -a is shortand for -auth-file ?
… Le 19 mai 2017 à 19:24, Gabriel Le Breton ***@***.***> a écrit :
invalid argument "uth-file...
uth-file?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
thanks @GabLeRoux ! |
I'm running this with the following:
Authentication works for the UI but the websockets are unable to connect due to http auth and get a 401 error. Any advice? If I disable the |
@tanc Try in Chrome. |
Hi,
Is there currently a way to have an authentification (at least Basic Auth) for the UI?
Thanks.
The text was updated successfully, but these errors were encountered: