Schema Architecture - Novell IDENTITY MANAGER DRIVER FOR ID PROVIDER 3.6.1 - IMPLEMENTATION Manual

All events are tracked and stored in the Identity Vault.
Scenario 2: Using an LDAP Database to Store the ID Provider Policies
This scenario allows you to use an LDAP database to store the ID Provider policies instead of using
the Identity Vault. Figure 1-2
LDAP Database Stores the ID Provider Policies
Figure 1-2
Identity
Vault
[root]
data
users
user1
user2
New user
1. A new User object is created in the Identity Vault, then the ID Provider driver picks up the
Create event.
2. The ID Provider driver reads the last ID that was generated from the ID Provider policies in the
LDAP database. The ID is then written back to the ID Provider policies in the LDAP database
to track the unique IDs.
3. The ID Provider driver then assigns the new ID to the new User object in the Identity Vault.

1.3 Schema Architecture

The Identity Vault's schema must be extended to support the ID Provider driver functionality. The
following two tables describe the schema attributes and classes.
shows how a unique ID is generated with the LDAP database.
read last ID from
IDM
policy, generate new
Engine
ID and write back
add
1
event
3
ID
LDAP
Directory
new ID to policy
2
[root]
system
Understanding the ID Provider Driver
services
ID Policies
policies1
policies2
policies3
11