My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Thanks,
Fred Bbaale +256772499474
On 04/01/13 22:28 +0300, Bbaale Fred wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Fred Bbaale
What difference, if any, do you see in a user's entry (using ldapsearch) before and after running ldappasswd on it?
--On Monday, April 01, 2013 10:28 PM +0300 Bbaale Fred bbaale@gmail.com wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
were they in crypt format, and you changed operating systems?
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
The attribute is different after running ldappasswd on it even thought I am pretty sure that its the same password.
I still have the ldiff file. If I decoded the userPasswords in the ldiff file and did a slapadd again, would it work?
Thanks Fred Bbaale
On Apr 1, 2013, at 10:46 PM, Dan White dwhite@olp.net wrote:
On 04/01/13 22:28 +0300, Bbaale Fred wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Fred Bbaale
What difference, if any, do you see in a user's entry (using ldapsearch) before and after running ldappasswd on it?
-- Dan White
Some password where is crypt format and some in SMD5.
Thanks,
Sent from my iPad
On Apr 1, 2013, at 10:48 PM, Quanah Gibson-Mount quanah@zimbra.com wrote:
--On Monday, April 01, 2013 10:28 PM +0300 Bbaale Fred bbaale@gmail.com wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
were they in crypt format, and you changed operating systems?
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
--On Monday, April 01, 2013 10:55 PM +0300 Bbaale Fred bbaale@gmail.com wrote:
Some password where is crypt format and some in SMD5.
Please don't top post.
I suggest you read http://www.openldap.org/faq/data/cache/344.html. Crypt passwords may not be portable, it is rather unwise to use them.
--Quanah
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration
On 04/01/13 22:55 +0300, Bbaale Fred wrote:
The attribute is different after running ldappasswd on it even thought I am pretty sure that its the same password.
I still have the ldiff file. If I decoded the userPasswords in the ldiff file and did a slapadd again, would it work?
What format are the passwords in, in your original slapcat'd file (after uudecoding)? Do they contain a prefix ({crypt})?
On Apr 1, 2013, at 10:46 PM, Dan White dwhite@olp.net wrote:
On 04/01/13 22:28 +0300, Bbaale Fred wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Fred Bbaale
What difference, if any, do you see in a user's entry (using ldapsearch) before and after running ldappasswd on it?
-- Dan White
On 04/01/13 22:55 +0300, Bbaale Fred wrote:
The attribute is different after running ldappasswd on it even thought I am pretty sure that its the same password.
I still have the ldiff file. If I decoded the userPasswords in the ldiff file and did a slapadd again, would it work?
What format are the passwords in, in your original slapcat'd file (after uudecoding)? Do they contain a prefix ({crypt})?
They do not have ({crypt}) . Slapcat produced base64 userPassword values, which i slapadd'ed .
On Apr 1, 2013, at 10:46 PM, Dan White dwhite@olp.net wrote:
On 04/01/13 22:28 +0300, Bbaale Fred wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Fred Bbaale
What difference, if any, do you see in a user's entry (using ldapsearch) before and after running ldappasswd on it?
-- Dan White
-- Dan White
On 04/01/13 23:16 +0300, Bbaale Fred wrote:
On 04/01/13 22:55 +0300, Bbaale Fred wrote:
The attribute is different after running ldappasswd on it even thought I am pretty sure that its the same password.
I still have the ldiff file. If I decoded the userPasswords in the ldiff file and did a slapadd again, would it work?
What format are the passwords in, in your original slapcat'd file (after uudecoding)? Do they contain a prefix ({crypt})?
They do not have ({crypt}) . Slapcat produced base64 userPassword values, which i slapadd'ed .
What are the first few characters of the password once base64 encoding has been removed? What 'password-hash' do you have configured in your config?
On Apr 1, 2013, at 10:46 PM, Dan White dwhite@olp.net wrote:
On 04/01/13 22:28 +0300, Bbaale Fred wrote:
My users can not login after a successful database migration from ldbm to bdb.
I did slapcat and slapadd my ldiff file sucessfully, but the userPassword attribute seems to have been modified.
Now for a user to login, i have to first change their password, or at least appear to do that. After doing a ldappasswd, even with the old password, the user can login.
Your help is needed , as I do not want to change passwords for 2000 users.
Fred Bbaale
What difference, if any, do you see in a user's entry (using ldapsearch) before and after running ldappasswd on it?
--On Monday, April 01, 2013 10:55 PM +0300 Bbaale Fred bbaale@gmail.com wrote:
Some password where is crypt format and some in SMD5.
Please don't top post.
I suggest you read http://www.openldap.org/faq/data/cache/344.html. Crypt passwords may not be portable, it is rather unwise to use them.
--Quanah
Thanks. My apologies for topping post. Let me try decoding and adding back. Hope it can help.
Fred.
--
Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc.
Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org
-
Bbaale Fred -
Dan White -
Quanah Gibson-Mount