Blackboard is similar to eDirectory in the way information is organized with the exception of Blackboard Enrollments.
User objects in eDirectory map directly to Person objects in Blackboard. Group objects in eDirectory map directly to Course and Organization objects in Blackboard. Course and Organization objects are differentiated by the OBNDBKBDDC-sub-evt-DetermineBBObjectType Event Transform Policy. Blackboard Enrollments have additional attributes that eDirectory Group memberships do not support. Two options exist to represent Enrollments in eDirectory:
The suggested best practice is to create a Blackboard Enrollment Object using the DirXML-BB-Enrollment object class in eDirectory for each enrollment in Blackboard.
The other option is to use the Group Member and Owner attributes to represent enrollments in Blackboard. The disadvantage of using the Member and Owner attributes is that enrollments can only be removed rather than being disabled.
While eDirectory is hierarchical, Blackboard is flat—there is no concept of a move function. The Subscriber channel rejects move commands. The sample Subscriber Event policy vetoes move events. You can change this policy to perform installation-specific processing of move events if required.
User object deletions in eDirectory result in the associated Person object in Blackboard being deleted. Group object deletions in eDirectory result in the associated Course or Organization object in Blackboard being deleted. There is no concept of rename in Blackboard. Blackboard is not hierarchical. There is no move function.
Identity Manager uses the nspmDistributionPassword attribute to provide passwords from eDirectory. The mapping policy in the preconfigured sample policies maps nspmDistributionPassword to DirXML-BB-p-password. The password is md5-hashed by the Driver Shim before being stored into Blackboard. The driver will also accept a md5-hashed password if mapped to the DirXML-BB-p-hashed-password attribute.