Results 1 to 3 of 3
Just installed Open-Xchange on Suse 10, and am having a hell of a time with LDAP, adding a user. To date I have yet to find an answer, and after ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 08-11-2006 #1Just Joined!
- Join Date
- May 2005
- Posts
- 52
Suse 10- invalid DN - Can not add user to LDAP
Just installed Open-Xchange on Suse 10, and am having a hell of a time with LDAP, adding a user. To date I have yet to find an answer, and after scrolling through the internet I do seem to see a lot of issues concerning LDAP and Suse's install.
adduser_ox
--username=sam
--passwd=system
--name=Sam
--sname=Sam
--maildomain=sam.com
--ox_timezone=Europe/Berlin
invalid DN
From SLAPD.CONF:
suffix "dc=sam,dc=com"
rootdn "uid=Admin,dc=sam,dc=com"
From etc/open-xchange/admintools.conf"
# LDAP Admin
BINDDN="uid=Admin,dc=sam,dc=com"
# LDAP Admin Passwd
BINDPW="secret"
Running "ldapsearch -x -W -D uid=Admin,dc=sam,dc=com" is successful giving me a full listed for "Admin"
I have run a search and replace of:
admintools.conf
slapd.conf
init_ldap.ldif
openxchange.schema
To insure that "sam.com" has replaced every instance of "example.org"
An LDAP browser fetchs a base DN of dc=sam,dc=com, and I can log into LDAP using "uid=Admin,dc=sam,dc=com" just fine. So what could cause the "invalid DN" for "sam.com" be?
Where are the LDAP logs under Suse 10? They seem to be non-existant
Also, why would I get "Invalid credentials (49) when doing a search for a user that I can not add?
Suse10:/ # ldapsearch -x -W -D uid=sam,dc=sam,dc=com
Enter LDAP Password:
ldap_bind: Invalid credentials (49)
- 08-27-2006 #2Just Joined!
- Join Date
- Apr 2005
- Posts
- 62
try to use cn instead of uid
or the part uid=sam, should it really be sam, might be a typo..Code:Suse10:/ # ldapsearch -x -W -D cn=sam,dc=sam,dc=com
Code:Suse10:/ # ldapsearch -x -W -D uid=admin,dc=sam,dc=com
- 09-15-2006 #3
This was a big help for me. Thanks so much!
Here's something that changes a user's password and clears the password expiration bit.
# Given that OP1 is the user's old password
# Given that P1 is the user's new password
# Given that this is the right dn for the user -- in this example it's $USER@sam.com. You'll have to adjust that.
# For instance, in my office, we have to use 'uid=$USER,ou=users,dc=ace,dc=motorola,dc=com'
ldappasswd -D "uid=$USER,dc=sam,dc=com" -x -w "$OP1" -s "$P1" "uid=$USER,dc=sam,dc=com"
echo -e "dn:uid=$USER,dc=sam,dc=com\nreplace:shadowLastCha nge\nshadowLastChange:$((`date '+%s'` / 86400))" | ldapmodify -x -w "$P1" -D "uid=$USER,dc=sam,dc=com"


Reply With Quote
