[Dovecot] Usernames and Passwords for Virtual Users Request
A feature I think would be nice.
When a single IP hosts email for multiple domains the solution is usually to use the complete email address as the username. I have users that have migrated from Cobalt RAQ's which do not work like that.
If a user trys to authenticate with just there username such as "joeb" instead of joeb@dirt.com I would like Dovecot to check all the domains it hosts and if it only finds one with the username "joeb" assume thats the one. If multiple domains have the username "joeb" refuse to authenticate without the "@domain" part.
Perhaps this is not possible. Sure would be handy though. Oh, it would also be nice to automatically lowercase all usernames before authentication.
Matt
Matt wrote:
If a user trys to authenticate with just there username such as "joeb" instead of joeb@dirt.com I would like Dovecot to check all the domains it hosts and if it only finds one with the username "joeb" assume thats
Sadly, you told nothing about how you store your user data. I simply presume it's in some sql database.
I had the same problem when we converted from system users to user@domain logins. So I stored the system users that where used for mail in a separate column in the users table and used a query like
SELECT ... WHERE (user='%n' AND domain='%d') OR old_login='%u'
This will even work with multiple domains having the same username.
also be nice to automatically lowercase all usernames before authentication.
Use the substitution modifiers, e.g. %Lu
Jakob Hirsch wrote:
Sadly, you told nothing about how you store your user data. I simply presume it's in some sql database.
Actually he did, but you didn't recognize it as such. Here's the applicable quote:
I have users that have migrated from Cobalt RAQ's which do not work like that.
Under the Cobalt web-based GUI, each domain hosted on that box contains an independent collection of users (stored in a hashed structure under /home/.sites//domain/user), with, I believe, independent passwd files. It really is, as he described, something that would not fit into the neat user@domain.com model.
John
-- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747
John Peacock wrote:
Sadly, you told nothing about how you store your user data. I simply presume it's in some sql database. Actually he did, but you didn't recognize it as such.
No. I was talking about the new user database, which is not Cobalt.
Under the Cobalt web-based GUI, each domain hosted on that box contains an independent collection of users (stored in a hashed structure under /home/.sites//domain/user), with, I believe, independent passwd files. It
And users log in as "user"? I wonder then how it distinguishes between the same username in different domains.
Jakob Hirsch wrote:
John Peacock wrote:
Sadly, you told nothing about how you store your user data. I simply presume it's in some sql database.
Actually he did, but you didn't recognize it as such.
No. I was talking about the new user database, which is not Cobalt.
Under the Cobalt web-based GUI, each domain hosted on that box contains an independent collection of users (stored in a hashed structure under /home/.sites//domain/user), with, I believe, independent passwd files. It
And users log in as "user"? I wonder then how it distinguishes between the same username in different domains.
Did you fill in any of the auth_realms ?
--
-- Chris L. Franklin --
participants (4)
-
Chris L. Franklin
-
Jakob Hirsch
-
John Peacock
-
Matt