https://bugzilla.redhat.com/show_bug.cgi?id=171080
+++ This bug was initially created as a clone of Bug #170454 +++ Description of problem: if we have a topology like this AD1<->RHDS<->AD2, then groups/users created in AD2 will not be replicated to AD2. So we might need to consider supporting this. Version-Release number of selected component (if applicable): 7.1sp1 How reproducible: consistent Steps to Reproduce: 1. setup a replication topology like this AD1<->RHDS<->AD2. 2. add a group in AD1. 3. check to make sure the group is replicated to AD2 Actual results: not replicated Expected results: should be replicated. Additional info: attribute ntGroupCreateNewGroup is not present in the RHDS entry. if we have a topology like this AD1<->RHDS<->AD2, then groups/users created in AD1 will not be replicated to AD2. So we might need to consider supporting this.
batch update moving tickets to future
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/225
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.