mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #173] Feature request: Set auth credentials from env variables #115
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#115
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Leny1337 on GitHub (Sep 27, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/173
Like in the topic - it could be great to provide login and password using env variables (separate for UI and SMTP).
For example:
In the code - if those variables are present, then do not use AUTH_FILE.
@axllent commented on GitHub (Sep 27, 2023):
I'll see what I can do here 👍
@ulken commented on GitHub (Sep 28, 2023):
This would align perfectly with my setup and make things easier on my end as well 👍 Let me know if I can help.
@axllent commented on GitHub (Sep 29, 2023):
I have just released v1.9.4 which includes the ability to set both the web UI and SMTP credentials via the
MP_UI_AUTH&MP_SMTP_AUTHenvironment variables. The credentials are a space-separated string with the exact sameuser1:password1 user2:password2formats documented in the wiki. Obviously plain text passwords are not recommended :) Please have a test and let me know if this works for you? Thanks!@ulken commented on GitHub (Sep 29, 2023):
On fire 🔥
I'll give it a try later today and report back.
@ulken commented on GitHub (Oct 4, 2023):
Sorry for the late report. The weekend happened and then other things popped up (as they tend to do...). I started looking at it yesterday and then the deployment environment failed on me etc. etc.
Anyhow, I've now tested it with the UI and it worked flawlessly 👌
One thing: how do you sign out? 😅 Clear cookies/local storage?
@axllent commented on GitHub (Oct 4, 2023):
That's great news (that it's working, not deployment failures lol). It's basic auth, you don't log out, you just close your browser. That's about it, nothing special, no cookies. There is localstorage which is just some preferences, but not credentials.
I'm closing this issue as it appears to have resolved the original request 👍