How The Rule Works - Novell POLICY IN DESIGNER 3.5 - 09-18-2009 Manual

Policies in designer 3.5
Table of Contents

Advertisement

3 Expand the predefined rule.
4 Edit the action by double-clicking the Actions tab.
5 Delete [Enter DN of destination Organization] from the Specify string field.
6 Click the Edit the arguments icon
7 Select Text in the noun list.
8 Double-click Text to add it to the argument.
9 In the editor, add the parent container in the data store. The parent container must be specified
in LDAP format. Make sure all of the department containers are child containers of this DN,
then click OK.
10 Click Finish.
11 Save the rule by clicking File > Save.

8.19.3 How the Rule Works

This rule places User objects in proper department containers depending upon the value that is
stored in the OU attribute. If a User object needs to be placed and has the OU attribute available,
then the User object is placed in the uid=unique name,ou=value of OU attribute,dest-base.
The dest-base is a local variable. The DN must be the relative root path of the department containers.
It can be an organization or an organizational unit. The value stored in the OU attribute must be the
name of a child container of the dest-base local variable.
The child containers must be associated for the User objects to be placed. The value of the OU
attribute must be the name of the child container. If the OU attribute is not present, then this rule is
not executed.
The uid attribute of the User object is the first two letters of the Given Name attribute plus the
Surname attribute as lowercase. The rule uses LDAP format.
to launch the Argument Builder.
Using Predefined Rules 143

Advertisement

Table of Contents
loading

This manual is also suitable for:

Designer for identity manager 3.5

Table of Contents