LDAP server fails to start with proxy user
(Last modified: 14Nov2003)
This document (10073430) is provided subject to the disclaimer at the end of this document.
symptom
LDAP server fails to start with proxy user
fact
Novell eDirectory 8.6.2 for Linux
Novell eDirectory 8.6.2 for Solaris
Novell eDirectory 8.5 for Linux
Novell eDirectory 8.5 for Solaris
LDAP
LDAP Proxy User
symptom
Proxy identity 'CN[equal]Proxy.O[equal]Novell' cannot have a password Could not configure proxy context in ReadConfigFromDS, err [equal] failed authenticate on (-669) Could not update server configuration, err [equal] failed authentication (-669)
The /var/nds/ndsd.log file shows LDAP beginning to start, but never shows it starting.
cause
The proxy user does not have a null password attribute
symptom
netstat -an | grep 389 does not list the LDAP port as listening
fix
Create a proxy user with a null password attribute
symptom
"netstat -an | grep 389" does not list the LDAP port 389 as listening
fix
Create a proxy user with a null password attribute
This is done by creating a normal user object and making sure the "Assign NDS Password" is checked. At the "Set Password" dialog, just leave the password blank and click the "Set Password" button. Once you have created the LDAP proxy user, open the LDAP Group properites, click on the General tab, and select the newly created proxy user to populate the "Proxy Username" field.
document
Document Title: | LDAP server fails to start with proxy user |
Document ID: | 10073430 |
Solution ID: | NOVL81559 |
Creation Date: | 08Aug2002 |
Modified Date: | 14Nov2003 |
Novell Product Class: | Connectivity Products NetWare Novell eDirectory |
disclaimer
The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.