Hi all,
Ok, just need a quick-n-dirty way to enable a master user for a migration...
Reading the docs, I'm not sure what the bare minimum is I need to do this...
At: http://wiki2.dovecot.org/Authentication/MasterUsers
The Example config shows:
auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/passwd.masterusers master = yes pass = yes } passdb { driver = shadow } userdb { driver = passwd }
But, if I'm using a non-real user (just need a master user that can log in as all other users for the migration), do I need all three of these? Or just the first two? Or, just the first one?
I think I need the first two and not the last one, but am unsure. This is on a production system so don't want to break things, and I'm unfamiliar with using multiple passdb's...
Thanks,
Charles
Hello Charles,
the bare minimum ist just the first passdb entry auth_master_user_separator = * passdb { driver = passwd-file args = /etc/dovecot/passwd.masterusers master = yes pass = yes }
this will do the trick.
greetings dominik Am Freitag, den 29.05.2015, 09:03 -0400 schrieb Charles Marcus:
On 5/29/2015 9:25 AM, Dominik Breu <dominik@dominikbreu.de> wrote:
Thanks... so, just checking, was it normal to see a whole bunch of these errors for a few seconds after reloading the dovecot config:
Error: Auth worker sees different passdbs/userdbs than auth server. Maybe config just changed and this goes away automatically?
?
As the error shows, they did go away by themselves after about 10+ seconds...
Thanks again!
Charles
On 5/29/2015 9:25 AM, Dominik Breu <dominik@dominikbreu.de> wrote:
Ok, this isn't working, I'm getting auth failed when testing either with telnet or doing it in Thunderbird.
I tried both using the htpasswd method for generating the password in the passwd file, and when that failed, I also tried just putting the password in the file in plain text...
So... what am I missing/doing wrong?
Thanks,
Charles
On 5/29/2015 10:58 AM, Dominik Breu <dominik@dominikbreu.de> wrote:
Thanks dominik, but I figured out what I did wrong...
I changed the password using htpasswd again, but neglected to use the -s switch to tell it to use SHA1 encryption method (finally noticed the $apr1$ at the beginning of the encrypted passwd in the file)...
Changing the passwd again using the -s switch now it works...
:)
Thanks again!
Charles
participants (2)
-
Charles Marcus
-
Dominik Breu