#47769 Include a mechanism to add inetuser attribute automatically in users synced from Winsync.
Closed: wontfix by mreynolds. Opened by rmeggins.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 6): Bug 1084779

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

RFE Request
0. Proposed title of this feature request
Include a mechanism to add inetuser attribute automatically in users synced
from Winsync.
2. What is the nature and description of the request?
RHDS provides a way to run memberOf fix-up whenever users are synced from AD to
RHDS by enabling posixWinsyncCreateMemberOfTask. This never works because newly
synced users from winsync does not have inetuser objectclass automatically
added which is required by memberof fixup script.
We should include a mechnism to automatically add above said objectclass in all
users whenever user is synced.
3. How would the customer like to achieve this? (List the functional
requirements here)
An attribute in winsync plugin which will configured winsync to add inetuser
objectclass if that attribute value is true.
4. Is there already an existing RFE upstream or in Red Hat bugzilla?
No
5. How quickly does this need resolved? (desired target release)
Customer is looking for ASAP solution.
6. Does this request meet the RHEL Bug and Feature Inclusion Criteria (please
review)
Yes
6. List the affected packages
389-ds-base.
7. Would the customer be able to assist in testing this functionality if
implemented?
It can be locally tested, customer didnt mentioned if he will be ready to test.

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

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- 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/1101

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