Bug 153105 - Windows sync agreement is missing domain and group sync attributes
Windows sync agreement is missing domain and group sync attributes
Product: Red Hat Directory Server
Classification: Red Hat
Component: UI - General UI (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Boreham
Orla Hegarty
Depends On:
Blocks: 146020
  Show dependency treegraph
Reported: 2005-04-01 11:15 EST by David Boreham
Modified: 2008-08-11 19:17 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-26 13:35:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed Patch (52.31 KB, patch)
2005-04-13 16:58 EDT, Thomas E Lackey
no flags Details | Diff

  None (edit)
Description David Boreham 2005-04-01 11:15:02 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

Description of problem:
The sync agreement needs to have these attributes:

nsds7NewWinGroupSyncEnabled: on
nsds7WindowsDomain: magpie.com

The console code currently doesn't add these.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.create agreement
2.observe that it is missing the aforementioned attrs

Additional info:
Comment 1 Thomas E Lackey 2005-04-13 16:58:53 EDT
Created attachment 113119 [details]
Proposed Patch

In addition to fixing the issue at hand, this patch cleans up some of the
labels which incorrectly referenced a sync agreement as a replication
Comment 2 David Boreham 2005-04-14 11:50:51 EDT
This is now fixed.
Comment 3 Thomas E Lackey 2005-05-26 13:34:39 EDT
Confirmed by QA with build 20050518.3.qa and build 20050523.1.qa.

Covered via console sync testing.
Comment 4 Chandrasekar Kannan 2008-08-11 19:17:55 EDT
Bug already CLOSED. setting screened+ flag

Note You need to log in before you can comment on or make changes to this bug.