#610 [RFE] Deleted posix attributes and object classes not synced from AD to DS
Closed: wontfix by mreynolds. Opened by nkinder.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 913092

Description of problem:
When the posix attributes and objectClass are deleted from Active Directory
with Windows sync and Winsync POSIX plugin active, this change is not
synchronized to DS.
Version-Release number of selected component (if applicable):
389-ds-base-1.2.11.15-10
How reproducible:
Steps to Reproduce:
1. Set up Windows synchronization and POSIX Windows Sync plugin
2. Add user or group entry with POSIX attributes
3. Delete POSIX attributes and entry's respective objectClass from AD
4. After sync (dependent on sync agreement) check the entry on DS
Actual results:
Attributes are not changed. Applies to both posixAccount and posixGroup object
classes and their respective attributes.
Expected results:
Attributes and object class should be deleted.
Additional info:
As mentioned in [1], there is no backlog for changes on AD. In that case the
posix winsync plugin iterates over the attributes in the actual active
directory entry. When the posix attributes are deleted, plugin can't iterate
over them and the attributes on DS entry are left unchanged.
[1]: https://github.com/cgrzemba/Posix-Winsync-Plugin-for-389-directory-server/
blob/master/posix-winsync.c

Metadata Update from @nkinder:
- Issue set to the milestone: FUTURE

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue tagged with: RFE

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

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/610

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