https://bugzilla.redhat.com/show_bug.cgi?id=158369
The attribute mapping for groups in the sync code includes a number of attributes that are not actually legal on 'group' objects. They are legal on other object classes that groups may have in AD, but not on the bare group object class. Examples: l, ou, o. If someone creates an entry in DS that is an ntGroup, and also has one or more of these attributes, but is not also an ou, the sync'ed entry add will fail on AD because of a schema violation.
batch move to milestone future
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @nkinder: - Issue set to the milestone: FUTURE
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to None (was: Needs Review) - 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/229
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.
Login to comment on this ticket.