LDAP user import to iPrint Appliance fails to import users/groups after admin password change.

  • 7016965
  • 05-Nov-2015
  • 05-Nov-2015

Environment

Novell iPrint Appliance 1.1 patch 3 (.418 version)

Situation

LDAP User import sync process stops working after the admin password is changed using iManager.

Resolution

Change the admin user password using the recommended tool, the iprint_edir_change_passwd.sh script.

See the iPrint Appliance documentation for details on this tool.

The basic steps are:
  • At appliance console run:
/opt/novell/bin/iprint_edir_change_passwd.sh
  • Enter the current eDirectory Admin password when prompted.
  • Enter the desired new eDirectory Admin password when prompted.
  • Re-enter the desired new eDirectory Admin password when prompted.

Cause

Changing the Admin user password using iManager is not recommended with the iPrint Appliance.

Additional Information

The mysql database shows that users/groups were imported, but they were not present within the Appliance eDirectory database. The ipmigrate.log file shows the following error:

Traceback (most recent call last):
  File "ldapservice.py", line 38, in Connect
  File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 199, in simple_bind_s
    return self.result(msgid,all=1,timeout=self.timeout)
  File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 428, in result
    res_type,res_data,res_msgid = self.result2(msgid,all,timeout)
  File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 432, in result2
    res_type, res_data, res_msgid, srv_ctrls = self.result3(msgid,all,timeout)
  File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 438, in result3
    ldap_result = self._ldap_call(self._l.result3,msgid,all,timeout)
  File "/usr/lib64/python2.6/site-packages/ldap/ldapobject.py", line 96, in _ldap_call
    result = func(*args,**kwargs)
INVALID_CREDENTIALS: {'info': 'NDS error: failed authentication (-669)', 'desc': 'Invalid credent

Feedback service temporarily unavailable. For content questions or problems, please contact Support.