389-ds-base

#49311 ldappasswd as directory manager gives "no such entry error".
Closed: wontfix by spichugi. Opened by firstyear.

Closed: wontfix
Reopen Issue

Issue Description

During an extended password operation as the rootdn account, we receive ldap.NO_SUCH_OBJECT. This is likely a quirk in how we attempt to perform the password change.

pwd_root_extop.py

Test case demonstrating the incorrect behaviour.

Metadata Update from @firstyear:
- Custom field type adjusted to defect

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.3.7 backlog

Metadata Update from @mreynolds:
- Issue set to the milestone: FUTURE (was: 1.3.7 backlog)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/2370

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.