Sync maps attributes for group entries that may be invalid in AD

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/229

• Created at 2012-01-10 01:41:26 by rmeggins (@richm)
• Closed at 2020-04-01 17:40:49 as wontfix
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=158369

---

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.

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-01-10 06:14:50

batch move to milestone future

[389-ds-bot]

Comment from rmeggins (@richm) at 2012-08-14 19:57:05

set default ticket origin to Community

[389-ds-bot]

Comment from nkinder (@nkinder) at 2012-08-28 04:14:50

Added initial screened field value.

[389-ds-bot]

Comment from nkinder (@nkinder) at 2017-02-11 23:07:40

Metadata Update from @nkinder:

• Issue set to the milestone: FUTURE

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-04-01 17:40:50

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None (was: Needs Review)
• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)