Novell Documentation: Nsure Identity Manager Drivers

Default Driver Configuration

Data Flow

Policies

Policies are used to control data synchronization between the Active Directory and eDirectory.

During the driver configuration, the Active Directory configuration file enables you to select several options that affect the default policies and filters created for you. The following table contains a list of these options and how they affect policy and filter creation:

Option	Description
	Configure Data Flow establishes the Filters on the Publisher and Subscriber channels. Bi-directional enables the same filters on both channels. Both channels receive the same set of default objects and attributes. AD to eDirectory places a restrictive filter so changes are not sent from eDirectory to Active Directory. eDirectory to AD places a restrictive filter so changes are not sent from Active Directory to eDirectory.
	This controls how objects are placed in eDirectory. Mirrored places objects in the same hierarchy as they exist in Active Directory. Flat places all objects in the base container specified during configuration.
	This controls how objects are placed in Active Directory. Mirrored places objects in the same hierarchy as they exist in eDirectory. Flat places all objects in the base container specified during configuration.

Option

Description

Configure Data Flow

Configure Data Flow establishes the Filters on the Publisher and Subscriber channels.

Bi-directional enables the same filters on both channels. Both channels receive the same set of default objects and attributes.

AD to eDirectory places a restrictive filter so changes are not sent from eDirectory to Active Directory.

eDirectory to AD places a restrictive filter so changes are not sent from Active Directory to eDirectory.

Publisher Placement

This controls how objects are placed in eDirectory.

Mirrored places objects in the same hierarchy as they exist in Active Directory.

Flat places all objects in the base container specified during configuration.

Subscriber Placement

This controls how objects are placed in Active Directory.

Mirrored places objects in the same hierarchy as they exist in eDirectory.

Flat places all objects in the base container specified during configuration.

The following table contains a list of the default policies and how they are affected by your selections during configuration:

Policy	Description
Create	In order for an Active Directory user to be created as a user in eDirectory, Full Name must be defined. 注: This is enforced in the create policy for a flat hierarchy, and the matching policy for a mirrored hierarchy. In either hierarchy, Full Name must be defined.
Matching	In a flat hierarchy, the matching policy attempts to match the user with an object with the same Full Name in the base container you specify. In a mirrored hierarchy, the matching policy attempts to match the user with an object with the same Fully Distinguished Name.
Placement	In a flat hierarchy, the placement policy places all objects in the base container you specify. In a mirrored hierarchy, the placement policy places all objects in a hierarchy that mirrors that of the data store sending the operation.

Policy

Description

Create

In order for an Active Directory user to be created as a user in eDirectory, Full Name must be defined.

注: This is enforced in the create policy for a flat hierarchy, and the matching policy for a mirrored hierarchy. In either hierarchy, Full Name must be defined.

Matching

In a flat hierarchy, the matching policy attempts to match the user with an object with the same Full Name in the base container you specify.

In a mirrored hierarchy, the matching policy attempts to match the user with an object with the same Fully Distinguished Name.

Placement

In a flat hierarchy, the placement policy places all objects in the base container you specify.

In a mirrored hierarchy, the placement policy places all objects in a hierarchy that mirrors that of the data store sending the operation.

Schema Mapping

The following eDirectory User and Group attributes are mapped to Active Directory user and group attributes:

eDirectory	Active Directory
CN	userPrincipalName in user cn in group
Description	description
DirXML-ADAliasName	sAMAccountName
Facsimile Telephone Number	facsimiletelephoneNumber
Full name	displayName
Given Name	givenName
Group Membership	memberOf
Initials	initials
Internet EMail Address	mail
L	physicalDeliveryOfficeName
Locality	locality
Login Allowed Time Map	logonHours
Login Disabled	dirxml-uACAccountDisable
Member	member
OU	ou
Owner	managedBy
Physical Delivery Office Name	l
Postal Code	PostalCode
Postal Office Box	postOfficeBox
S	st
SA	streetAddress
See Also	seeAlso
Surname	sn
Telephone Number	telephoneNumber
Title	title