#7610 ldapupdate.py users ldap.LOCAL_ERROR and other direct ldap exceptions while relying on ipaldap
Closed: fixed by abbra. Opened by abbra.

ipaserver/install/ldapupdate.py uses ldap.LOCAL_ERROR and ldap.INVALID_CREDENTIALS exceptions while calling an LDAP bind code from ipaldap which remaps these exceptions to ACIError.

The code in ipaldap got changed with df4ed77 but ldapupdate was never updated.


Near as I can tell only schema_update() uses ldapupdate.connect() and never passes in a DM password so looks like simple bind can be dropped altogether.

(ldap.CONNECT_ERROR, ldap.SERVER_DOWN): should be replaced by NetworkError

Metadata Update from @abiagion:
- Issue set to the milestone: FreeIPA 4.7.1
- Issue tagged with: easyfix

Metadata Update from @rcritten:
- Issue set to the milestone: FreeIPA 4.7.2 (was: FreeIPA 4.7.1)

FreeIPA 4.7.1 has been released, moving to FreeIPA 4.7.2 milestone

master:

  • e66036481477ec8efc27c697e8a0d7adaf8a691d Use ipaldap exceptions rather than ldap error codes in LDAP updater

Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

master:

  • 0f232a30116751f38722c65ae607c6e6958c8061 Remove unused support for dm_password arg from ldapupdate.connect
Metadata