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.

Description of problem:
WinSync currently deletes any matching user from 389 DS that it finds in a container outside of the configured container in AD.

Instead of deleting, I think we should just log a warning like
"Could not sync the AD entry %s with the DS entry %s, even though they have the same user id (or group id) %s, because the AD entry is out of scope %s of the windows sync agreement"
deleting perfectly good users is bad

see upstream ticket: https://fedorahosted.org/389/ticket/355

Version-Release number of selected component (if applicable):
1.2.10

How reproducible:
100%

Steps to Reproduce:
1. Configure 389 DS with duplicate users in AD & 389.  Place the duplicate AD users in a container B.
2. Configure 389 DS to utilize the WinSync plugin and configure it to look in Container A.
3. 389 will delete any matching user found inside of Container B.
  
Actual results:
Users are deleted

Expected results:
Perhaps a Warning error message indicating that users were found outside of the configured ldap container in Active Directory.

Additional info:

We are talking about the IPA version of the Winsync here. Changing component.

(In reply to comment #2)
> We are talking about the IPA version of the Winsync here. Changing component.

Problem affects core 389 too, without IPA.

Upstream ticket:
https://fedorahosted.org/389/ticket/2927

(In reply to comment #3)
> (In reply to comment #2)
> > We are talking about the IPA version of the Winsync here. Changing component.
> 
> Problem affects core 389 too, without IPA.

And the problem will have to be fixed in the core 389 winsync plugin.

Upstream ticket:
https://fedorahosted.org/389/ticket/355

(In reply to comment #4)
> Upstream ticket:
> https://fedorahosted.org/389/ticket/2927

This is a correct link to IPA upstream ticket:

https://fedorahosted.org/freeipa/ticket/2927

ipa spec file updated to pull in fixed version of 389-ds-base, 1.2.11.12.

*** This bug has been marked as a duplicate of bug 818762 ***