Hi Jesus,

There is something I'm not understanding in your problem:

Fact 1) This is your LDIF:

dn: [EMAIL PROTECTED],ou=acelerate_org,ou=qmail_users,dc=acelerate,dc=org
cn: Example.tld Admin
ou: acelerate_org
ou: qmail_users
sn: Admin
objectClass: top
objectClass: person
objectClass: inetOrgPerson
objectClass: qmailUser
mail: [EMAIL PROTECTED]
mailHost: mail.acelerate.org
mailQuotaSize: 0
mailQuotaCount: 0
uid: admin
accountStatus: active
userPassword: {MD5}Xr4ilOzQ4PCOq3aQ0qbuaQ==
mailMessageStore: /var/qmail/vpopmail/domains/mail.acelerate.org/postmaster
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]
mailAlternateAddress: [EMAIL PROTECTED]


Fact 2) This is how you are authenticating via POP:

I just patch qmail-ldap with this patch. but i still have to login using [EMAIL PROTECTED]

So you say that you have to use "[EMAIL PROTECTED]" to login. How come? This is impossible since your uid attribute is just "username". If your uid attribute is really "uid: admin", once you try to login with username "admin" and password "{MD5}Xr4ilOzQ4PCOq3aQ0qbuaQ==" the login has to be successful. Even if you didn't apply Kristof's patch, this have to work.

Aren't you making a mistake there? With the LDIF you presented, the authentication with "admin" and password "{MD5}r4ilOzQ4PCOq3aQ0qbuaQ==" has to work with or without his patch...

You will use this patch if you want to have two or more "uid: admin" in your DIT. Without this patch it is impossible, but with the patch they can exist if they're in different branches, and the IP->branch mapping was correctly done in control/ipvirtualbasedn file.

regards,
bnegrao

Reply via email to