Human Resource Driver Policies - Novell IDENTITY MANAGER 3.6.1 - WORKORDER DRIVER IMPLEMENTATION GUIDE 18-12-2009 Implementation Manual

Workorder driver implementation guide
Table of Contents

Advertisement

In this scenario, assume the new employee's name is Albert Hauser. Albert is hired, but does not
begin work until a future date and time. He is put into the HR system with the hire date set. Albert is
marked as not active and does not have access to the system.
The HR Identity Manager driver writes Albert's user object to the Identity Vault. A policy in that
driver checks to see if he is active. If he is active, the driver performs the work. If he is not active,
the policy creates a work order to activate Albert's account on the hire date. The work order is
marked pending. A policy in the WorkOrder driver processes the work order on the hire date. The
policy in the WorkOrder driver sets the user object's loginDisabled attribute to False, allowingAlbert
to log in.
The sample could be extended to allow other Identity Manager drivers to have a Create rule to
disallow the creation of the user object in other connected systems until the user object's
loginDisabled attribute is set to False. The result is that the user's system access is provisioned on
his hire date and not before.

6.2.1 Human Resource Driver Policies

The following policies show how to implement this sample. In the sample, the WorkOrder driver is
acting as the HR system interface. The WorkOrder driver is configured to provide the needed
attributes: LastName, FirstName, HireDate, and Disabled.
Mapping Rule
The mapping rule maps the attributes used in the WorkOrder driver to attributes in the Identity Vault.
You can view the sample at
hr-drv-schema-map.xml (http://www.novell.com/documentation/
idm36drivers/work_order/samples/hr-drv-schema-map.xml).
Filter
The filter attribute allows only the attributes that are needed by this example to be passed through.
The DirXML-DueDate is notify only. This attribute should not be applied to the user object.
However, it should be available for the Command Transformation. You can view the sample at
hr-
drv-schema-map.xml (http://www.novell.com/documentation/idm36drivers/work_order/samples/hr-
drv-filter.xml)
Command Transformation Policy
The Command Transformation policy checks to see if a user object is being added to the Identity
Vault. It also ensures that the loginDisabled attribute is set to True. If the conditions are satisfied, the
policy then creates a work order and places it in the WorkOrder container. The WorkOrder driver
looks in this container for work orders to process. The policy puts the DN of the user that was
created into the DirXML-nwoContent attribute. You can view the sample at
hr-drv-cmd-
transform.xml (http://www.novell.com/documentation/idm36drivers/work_order/samples/hr-drv-
cmd-transform.xml).
A second policy puts the DirXML-DueDate from the user into the WorkOrder object DirXML-
DueDate and then sets the work order status to Pending. You can view the sample at
hr-drv-cmd-
transform2.xml (http://www.novell.com/documentation/idm36drivers/work_order/samples/hr-drv-
cmd-transform2.xml).
32
Identity Manager 3.6.1 WorkOrder Driver Implementation Guide.

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the IDENTITY MANAGER 3.6.1 - WORKORDER DRIVER IMPLEMENTATION GUIDE 18-12-2009 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Identity manager 3.6.1

Table of Contents