Bug 700200 - Active Directory has certain uids which are reserved and will cause a Directory Server replica initialization of an AD server to abort.
Summary: Active Directory has certain uids which are reserved and will cause a Directo...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: 389
Classification: Retired
Component: Sync Service
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Rich Megginson
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks: 690319
TreeView+ depends on / blocked
 
Reported: 2011-04-27 18:28 UTC by Stuart R. Kirk
Modified: 2015-01-04 23:48 UTC (History)
6 users (show)

Fixed In Version: 389-ds-base-1.3.2.0-1.fc20
Clone Of:
Environment:
Last Closed: 2013-12-18 19:39:19 UTC
Embargoed:


Attachments (Terms of Use)
List of reserved words that AD can not have as a uid. (772 bytes, text/plain)
2011-04-27 18:28 UTC, Stuart R. Kirk
no flags Details

Description Stuart R. Kirk 2011-04-27 18:28:29 UTC
Created attachment 495309 [details]
List of reserved words that AD can not have as a uid.

Description of problem:
There are a list of reserved UIDs within Active Directory which cannot be synchronized from RHDS to AD.  If a uid within RHDS is equal to one of these values, the initialization of the AD consumer will fail to complete.

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

How reproducible:
100%

Steps to Reproduce:
1. Create an account in an RHDS with a sync agreement to an AD consumer.
2. Enter one of the prohibited words that Active Directory won't allow to be a uid.
3. Initiate a full sync.
  
Actual results:
When the user in question is encountered, the following message appears in /var/log/dirsrv/slapd-<instance>/errors:
[27/Apr/2011:13:04:42 -0500] NSMMReplicationPlugin - agmt="cn=ADSync" (huey:389): windows_tot_run: failed to obtain data to send to the consumer; LDAP error - -1

In our case, we used the uid "service".

Expected results:
I would like to see RHDS log the error however continue on with the initialization rather than aborting.

Additional info:

Comment 1 Stuart R. Kirk 2011-04-27 19:51:03 UTC
In addition, it would be nice if RHDS could parse the entire database of users within it to determine if any of these words exist prior to a winsync init operation.  If they exist, an alert should be generated.  Would be nice to incorporate that into the syntax-validate.pl script as a caveat for Winsync.

Comment 4 Martin Kosek 2012-01-04 13:23:52 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/48

Comment 5 Nathan Kinder 2013-12-18 19:39:19 UTC
This was fixed in 389-ds-base-1.3.2.0-1.fc20.


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