Cisco Cisco Unified MeetingPlace Directory Services Manuale Di Manutenzione
Chapter
5
Managing
MeetingPlace
Directory
Services 39
Latitude
Communications
MeetingPlace
Directory
Services
System
Manager’s
Guide
Once
a MetaLink agreement is run, correlation is used to
determine
if the entry, or profile, already exists in MeetingPlace.
If
the profile does exist, standard synchronization uses standard
attribute
mapping to update the profile with the information from
your
corporate directory server.
If
the profile does not exist, correlation uses BootStrap attribute
mapping
to create a new profile. BootStrap attribute mapping is
an
effective way to perform certain mappings when an entry is
first
imported into MeetingPlace.
For
example, in BootStrap attribute mapping you can map the
password
attribute to a generic value of 1234. When a
MeetingPlace
profile is created initially, it will be assigned a
password
value of 1234. When a user logs into MeetingPlace for
the
first time, he can access his profile using this generic
password.
Once the user accesses his profile, he can change the
password
to a more secure password. Since BootStrap attribute
mapping
only occurs when a profile is first created, it will not
perform
updates to profiles that already exist in MeetingPlace.
When
you create attribute mappings, you can specify that an
attribute
must have a value before it gets propagated to
MeetingPlace.
The % sign preceding an attribute ensures that the
attribute
value is mandatary.
For
example, you can map %LastName=sn so that last name
attribute
on the source server is mapped to the sn attribute on the
destination
server. The % sign guarantees that the last name
attribute
must have a value to be propagated to MeetingPlace. If
the
attribute does not have a value, an error will be written to the
suspense
file, and the gateway will proceed to the next entry in
the
directory.