User/group entries added to DS do not have their posix attributes synced to AD. This is due to a limitation in the winsync v1 api. The v2 and later api support a pre add callback for DS to AD entries.
Added initial screened field value.
this adds sync of posix attributs from DS to AD for new entries (tested in version 1.2.11.15) 0010-ticket-428-add-initial-sync-from-DS-to-AD.patch
Description: User/group entries added to DS do not have their posix attributes synced to AD. This is due to a limitation in the winsync v1 api. The v2 and later api support a pre add callback for DS to AD entries.
This patch was originally provided by From: Carsten Grzemba cgrzemba@opencsw.org Date: Fri, 25 Jan 2013 14:59:32 +0100 Subject: ticket 428: add initial sync from DS to AD Thank you for your contribution, Carsten!
It was reviewed and couple of minor bugs were fixed by nhosoi. 1) Commented out posix_group_del_memberuid_callback in posix-group-task.c to clean up a compiler warning. 2) In posix_winsync_pre_ad_add_user_cb and posix_winsync_ pre_ad_add_group_cb, nisdomainname is added to the to-be-added-to-AD entry only if nisdomainname is given. 3) In +posix_winsync_pre_ad_add_group_cb, a local variable to scan array attr_map was unexpectedly shared with the outer for loop for getting attribute value.
git patch file (master) 0001-Ticket-428-posix-winsync-should-support-ADD-user-gro.patch
Reviewed by Rich (Thank you!!)
Pushed to master: commit 58234ad
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1044137
Metadata Update from @cgrzemba: - Issue assigned to nhosoi - Issue set to the milestone: 1.3.2 - 05/13 (May)
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/428
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.