https://bugzilla.redhat.com/show_bug.cgi?id=746645
In RHDS 8.2 (and 9.0 AFAIK), the only way to specify which attributes to synchronise from AD into RHDS is via writing a plugin (like IPA's ipa-winsync.c). It would be really nice to be able to configure, per sync agreement, which attributes should and should not be synchronised (and maybe even define the map between AD attribute names and RHDS attribute names).
batch update moving tickets to future
We should add this capability to allow posix attributes to be synchronized with AD.
set default ticket origin to Community
Added initial screened field value.
Metadata Update from @rmeggins: - 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/179
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.