Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #2000261 +++
This bug is created as a clone of upstream ticket:
https://pagure.io/freeipa/issue/8965
[description of the issue]
The fix for #8044 in commit 9fe984fed7a7091bd1366be95fdfa2f56f777bb8 replaced the LDAP_NO_SUCH_OBJECT error code at two places where it was actually correct. As a result lookups for UIDs or GIDs will return the generic LDAP_OPERATIONS_ERROR to clients if the UID or GID is coming from a different domain than the requested. Since the given UID or GID does not exists in the domain LDAP_NO_SUCH_OBJECT is the right return code and would help the client to act accordingly.
#### Steps to Reproduce
1. Setup IPA with trust to AD
2. Set the domain resolution order so that the trusted AD domain is looked up first
3. On an IPA client call `getent passwd UID_of_an_IPA_user` or `getent group GID_Of-IPA_group`
#### Actual behavior
With `debug_level = 9` in the `sssd_nss.log` messages like `Data Provider Error: 3, 1432158230, Network I/O Error` and in the backend log messages like `ldap_extended_operation result: Operations error(1), Failed to handle the request.` can be seen.
#### Expected behavior
Nss responder and backend log should just indicate that the given UID or GID is not present in the given domain.
#### Version/Release/Distribution
ipa-4.6 and above, all versions where fox for #8044 was applied.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (ipa bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:4230