Web UI - Authentification

[jygastaud]

Hi,

Is there currently a way to have an authentification (at least Basic Auth) for the UI?

Thanks.

[ian-kent]

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.

[grega]

👍 I'd love to have the option to require basic auth as well.

[ian-kent]

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!

[GabLeRoux]

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.

[hamrant]

MailHog -auth-file=docs/example-auth
flag provided but not defined: -auth-file

[ashleyhindle]

This is definitely working now, I imagine this issue can be closed

Example command: /usr/local/bin/mailhog -auth-file=/home/mailhog/auth -api-bind-addr='0.0.0.0:80' -ui-bind-addr='0.0.0.0:80' -smtp-bind-addr='0.0.0.0:25'

[ian-kent]

Thanks, glad it's working 👍

I'll keep the issue open for now as a reminder to make password handling less bcrypt-crazy

[klokie]

Nice!
Would you be able to explain how to enable basic auth via docker environment variables? I haven't figured that part out yet.

[fredleger]

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

entrypoint: MailHog -auth-file=/data/mailhog/auth.file

or on the command line just add "--entrypoint MailHog -auth-file=/data/mailhog/auth.file" to you docker run command.

[RuchyK]

@fredleger ,
Running this command:

➜  ~ sudo docker run --name=maildocker -d -it -p 1025:1025 -p 8025:8025 --entrypoint MailHog -auth-file=/data/mailhog/auth.file mailhog/mailhog

fails with this error:

 invalid argument "uth-file=/data/mailhog/auth.file" for auth-file=/data/mailhog/auth.file: valid streams are STDIN, STDOUT and STDERR

Any idea?
The location passed to auth-file is on the host machine or on the docker?

[GabLeRoux]

invalid argument "uth-file...
uth-file?

Maybe a typo on your side with docker command line?

Details about authentification can be found here:
https://github.com/mailhog/MailHog/blob/7ea7fe4/docs/Auth.md

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 --entrypoint thingy):

docker run --name=maildocker -d -it -p 1025:1025 -p 8025:8025 -v $(pwd):/data/mailhog/ mailhog/mailhog -auth-file=/data/mailhog/auth.file

Output from the container's logs:

2017/05/19 18:01:45 Using in-memory storage
[HTTP] Loaded 1 users from /data/mailhog/auth.file
2017/05/19 18:01:45 [SMTP] Binding to address: 0.0.0.0:1025
[HTTP] Binding to address: 0.0.0.0:8025
2017/05/19 18:01:45 Serving under http://0.0.0.0:8025/
Creating API v1 with WebPath: 
Creating API v2 with WebPath: 
[APIv2] GET /api/v2/jim
[APIv2] GET /api/v2/messages
[APIv2] GET /api/v2/websocket
[APIv1] KEEPALIVE /api/v1/events

[fredleger]

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.

[RuchyK]

thanks @GabLeRoux !
docker solution worked!!

[tanc]

I'm running this with the following:

/usr/local/bin/mailhog \
  -api-bind-addr 78.157.123.28:8025 \
  -ui-bind-addr 78.157.123.28:8025 \
  -smtp-bind-addr 127.0.0.1:1025 \
  -auth-file=/etc/mailhog/auth.file

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 -auth-file then it all works.

[fabiofdsantos]

@tanc Try in Chrome.