Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export or import deliverables. You agree not to export or re-export to entities on
the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws.
You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. See the
Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information on
exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the latest online documentation for this and other Novell products, see
the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html).
Third-Party Materials
All third-party trademarks are the property of their respective owners.
Novell® Identity Manager 3.6.1 is a data sharing and synchronization service that enables
applications, directories, and databases to share information. It links scattered information and
enables you to establish policies that govern automatic updates to designated systems when identity
changes occur.
Identity Manager provides the foundation for account provisioning, security, single sign-on, user
self-service, authentication, authorization, automated workflows, and Web services. It allows you to
integrate, manage, and control your distributed identity information so you can securely deliver the
right resources to the right people.
This guide provides detailed information on using Designer 3.0 for Identity Manager 3.6.1.
Chapter 1, “Overview,” on page 17
Chapter 3, “Managing Policies with the Policy Builder,” on page 21
Chapter 4, “Using Additional Builders and Editors,” on page 45
Chapter 5, “Using the XPath Builder,” on page 71
Chapter 6, “Defining Schema Map Policies,” on page 77
novdocx (en) 13 May 2009
Chapter 7, “Controlling the Flow of Objects with the Filter,” on page 93
Chapter 8, “Using Predefined Rules,” on page 109
Chapter 9, “Testing Policies with the Policy Simulator,” on page 145
Chapter 10, “Storing Information in Resource Objects,” on page 169
Chapter 11, “Using ECMAScript in Policies,” on page 175
Chapter 12, “Conditions,” on page 189
Chapter 13, “Actions,” on page 233
Chapter 14, “Noun Tokens,” on page 313
Chapter 15, “Verb Tokens,” on page 353
There are additional reference chapters for the pre-Identity Manager Policy Builder:
Chapter 2, “Using the Pre-Identity Manager 3.5 Policy Builder,” on page 19
Chapter 16, “Pre-Identity Manager 3.5 Builders,” on page 375
Chapter 17, “Pre-Identity Manager 3.5 Conditions,” on page 391
Chapter 18, “Pre-Identity Manager 3.5 Actions,” on page 419
This guide is intended for Identity Manager administrators.
About This Guide15
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to www.novell.com/documentation/feedback.html and enter your
comments there.
Documentation Updates
For the most recent version of Policies in Designer, visit the Identity Manager Documentation Web
site (http://www.novell.com/documentation/idm35).
Additional Documentation
For documentation on using the Identity Manager drivers, see the Identity Manager Drivers
Documentation Web site (http://www.novell.com/documentation/idm36drivers/index.html).
For documentation on using Designer, see the Designer 3.0 for Identity Manager 3.6.1
Documentation Web site (http://www.novell.com/documentation/designer21/).
novdocx (en) 13 May 2009
Documentation Conventions
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
®
A trademark symbol (
, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* or UNIX*, should use forward slashes as required by your software.
16Policies in Designer 3.5
1
Overview
Policies manage the data that is synchronizing between the Identity Vault and the remote data store.
The policies are stored in the policy sets (see “Understanding Types of Policies” in Understanding
Policies for Identity Manager 3.6.) Designer provides a wide set of tools for defining and debugging
policies to control how information flows from one system to another, and under what conditions.
The following sections explain how to use the tools that are provided to help manage the policies:
Chapter 3, “Managing Policies with the Policy Builder,” on page 21
Chapter 4, “Using Additional Builders and Editors,” on page 45
Chapter 5, “Using the XPath Builder,” on page 71
Chapter 6, “Defining Schema Map Policies,” on page 77
Chapter 7, “Controlling the Flow of Objects with the Filter,” on page 93
Chapter 8, “Using Predefined Rules,” on page 109
Chapter 9, “Testing Policies with the Policy Simulator,” on page 145
novdocx (en) 13 May 2009
1
Chapter 10, “Storing Information in Resource Objects,” on page 169
Chapter 11, “Using ECMAScript in Policies,” on page 175
This section also contains a detailed reference section to all of the elements in DirXML® Script. For
more information on DirXML Script, see “DirXML Script DTD” in the Identity Manager 3.6 DTD
Reference.
Chapter 12, “Conditions,” on page 189
Chapter 13, “Actions,” on page 233
Chapter 14, “Noun Tokens,” on page 313
Chapter 15, “Verb Tokens,” on page 353
There are also reference sections for the pre-Identity Manager Policy Builder:
Chapter 2, “Using the Pre-Identity Manager 3.5 Policy Builder,” on page 19
Chapter 16, “Pre-Identity Manager 3.5 Builders,” on page 375
Chapter 17, “Pre-Identity Manager 3.5 Conditions,” on page 391
Chapter 18, “Pre-Identity Manager 3.5 Actions,” on page 419
As part of understanding how policies work, it is important to understand the components of
policies.
Policies are made up of rules.
A rule is a set of conditions (see Chapter 12, “Conditions,” on page 189) that must be met
before a defined action (see Chapter 13, “Actions,” on page 233) occurs.
Overview
17
Actions can have dynamic arguments that derive from tokens that are expanded at runtime.
Tokens are broken up into two classifications: nouns and verbs.
Noun tokens (see Chapter 14, “Noun Tokens,” on page 313) expand to values that are
derived from the current operation, the source or destination data stores, or some external
source.
Verb tokens (see Chapter 15, “Verb Tokens,” on page 353) modify the concatenated
results of other tokens that are subordinate to them.
Regular expressions (see “Regular Expressions”) and XPath 1.0 expressions (see “XPath 1.0
Expressions”) are commonly used in the rules to create the desired results for the policies.
A policy operates on an XDS document and its primary purpose is to examine and modify that
document.
An operation is any element in the XDS document that is a child of the input element and the
output element. The elements are part of the Novell
®
nds.dtd
; for more information, see
“NDS DTD” in the Identity Manager 3.6 DTD Reference.
An operation usually represents an event, a command, or a status.
The policy is applied separately to each operation. As the policy is applied to each operation in
turn, that operation becomes the current operation. Each rule is applied sequentially to the
current operation. All of the rules are applied to the current operation unless an action is
executed by a prior rule that causes subsequent rules to no longer be applied.
A policy can also get additional context from outside of the document and cause side effects
that are not reflected in the result document.
novdocx (en) 13 May 2009
18Policies in Designer 3.5
2
Using the Pre-Identity Manager 3.5
novdocx (en) 13 May 2009
Policy Builder
Designer contains two Policy Builders: the pre-Identity Manager 3.5 Policy Builder and the Identity
Manager 3.5 and Newer Policy Builder. The Policy Builders are similar except for the following:
You can enable and disable trace only at the driver level in the pre-Identity Manager 3.5 Policy
Builder.
The DirXML
These differences require two Policy Builders. For information on how to use both Policy Builders,
see Chapter 3, “Managing Policies with the Policy Builder,” on page 21, which documents the
Identity Manager 3.5 and Newer Policy Builder. The only difference is an additional icon that
enables and disables tracing on rules, actions, conditions, and tokens.
For a list of the DirXML Script elements for the pre-Identity Manager 3.5 Policy Builder:
Chapter 17, “Pre-Identity Manager 3.5 Conditions,” on page 391
Chapter 18, “Pre-Identity Manager 3.5 Actions,” on page 419
For a list of the DirXML Script elements for the Identity Manager 3.5 and Newer Policy Builder:
®
Script elements are different between the two builders.
2
Chapter 12, “Conditions,” on page 189
Chapter 13, “Actions,” on page 233
Chapter 14, “Noun Tokens,” on page 313
Chapter 15, “Verb Tokens,” on page 353
Using the Pre-Identity Manager 3.5 Policy Builder
19
novdocx (en) 13 May 2009
20Policies in Designer 3.5
3
Managing Policies with the Policy
novdocx (en) 13 May 2009
Builder
The Policy Builder is a complete graphical interface for creating and managing the policies that
define the exchange of data between connected systems.
Section 3.1, “Accessing the Policy Builder,” on page 21
Section 3.2, “Using the Policy Builder,” on page 23
Section 3.3, “Creating a Policy,” on page 24
Section 3.4, “Creating a Rule,” on page 28
Section 3.5, “Creating an Argument,” on page 33
Section 3.6, “Variable Selector,” on page 35
Section 3.7, “Editing a Policy,” on page 39
Section 3.8, “Viewing the Policy in XML,” on page 42
3.1 Accessing the Policy Builder
There are two different Policy Builders included in Designer 3.0: one that works with the new policy
features for Identity Manager 3.5 and newer, and an older one that does not support these features.
The Policy Builder version is determined by the version of Identity Manager. To set the version of
Identity Manager:
3
1 Open a project in Designer.
2 Click the Outline tab, then select the Show Model Outline icon .
3 Right-click the server object, then click Properties.
4 Select the appropriate Identity Manager Version.
When the Identity Manager version is set to 3.5 or newer, the new Policy Builder is available. If the
version is set to anything other than 3.5, the old Policy Builder is available.
The Policy Builder can be accessed from the Model Outline view, from the Policy Flow view, or
from a policy set.
Section 3.1.1, “Model Outline View,” on page 21
Section 3.1.2, “Policy Flow View,” on page 22
Section 3.1.3, “Policy Set,” on page 22
3.1.1 Model Outline View
1 Open a project in Designer.
2 Click the Outline view, then select the Show Model Outline icon .
3 Double-click a policy listed in the Model Outline view or right-click and select Edit.
Managing Policies with the Policy Builder
21
3.1.2 Policy Flow View
1 Open a project in Designer.
2 Select the Outline tab, then select the Show Policy Flow icon.
3 Double-click a policy in the Policy Flow view.
You can also right-click in the Policy Flow view, select Edit Policy, then select the policy you
want to edit.
3.1.3 Policy Set
1 Open a project in Designer.
2 Click the Outline view, then select the Show Model Outline icon.
3 Select the policy in the policy set, then click Edit the policy.
You can also right-click the policy in the policy set, then click Edit.
novdocx (en) 13 May 2009
To see all of the information in the Policy Builder window without scrolling, double-click the policy
tab so the Policy Builder fills the entire window. To minimize the window, double-click the policy
tab.
22Policies in Designer 3.5
Figure 3-1 Policy Builder Full Screen
novdocx (en) 13 May 2009
For information on using the Policy Builder, see Section 3.2, “Using the Policy Builder,” on
page 23.
3.2 Using the Policy Builder
The Policy Builder enables you to add, view, and delete the rules that make up a policy. You can also
use it to import and save policies and rules, and manage XML namespaces. The Policy Builder
contains the “Action Builder” on page 45 and the “Condition Builder” on page 52.
The following tips describe how to perform some common Policy Builder tasks:
Table 3-1 Common Policy Builder Tasks
TasksDescription
DisableDisables a policy, rule, condition, or action.
EnableEnables a policy, rule, condition, or action.
Disable TraceDisables tracing on a rule, condition, or action.
Enable TraceEnables tracing on a rule, condition, or action.
in the tool barEnables DirXML Script tracing on the policy.
EditEdits the name of a rule or edits the description of a
rule.
DeleteDeletes a rule or a policy.
BrowseBrowses a list of values to use when populating a
field.
Managing Policies with the Policy Builder23
TasksDescription
Add a rule Adds a new rule or a predefined rule.
ImportImports a policy from a file.
Save to FileSaves a policy to a file.
DeployDeploys a policy to the Identity Vault.
CompareCompares the policy in the Policy Builder to an
existing policy in the Identity Vault.
Policy SimulatorLaunches the Policy Simulator and tests the
policies in the Policy Builder.
Edit NamespaceAdds multiple XML namespaces to the rule or
policy.
XPath BuilderLaunches the XPath Builder to create XPath
expressions.
ExpandExpands all of the rules in a policy.
novdocx (en) 13 May 2009
CollapseCollapses all of the rules in a policy.
Move upMoves a rule up in the policy.
Move downMoves a rule down in the policy.
SaveClick the save icon in the tool bar, click File > Save,
or press Ctrl+S to save your work.
Policy DescriptionAdds a comment to a policy or rule. Comments are
stored directly in the policy or rule, and can be as
long as necessary.
3.3 Creating a Policy
A policy sends data to the connected systems. A policy is created through the policy set.
Section 3.3.1, “Accessing the Policy Set,” on page 24
Section 3.3.2, “Using the Policy Set,” on page 25
Section 3.3.3, “Using the Add Policy Wizard,” on page 26
3.3.1 Accessing the Policy Set
1 Select a driver object from the Outline view in an open project.
24Policies in Designer 3.5
2 Select the Policy Set tab.
3.3.2 Using the Policy Set
The policy set contains a toolbar and a list of policies.
The policy list displays all the policies contained in the selected policy set. During a transformation,
the policies within the list are executed from top to bottom. The toolbar contains buttons and a dropdown menu that you can use to manage policies displayed in the list, including, editing, adding,
deleting, renaming, and changing the processing order of the policies.
novdocx (en) 13 May 2009
Policy Set Toolbar
The policy set displays a copy of the policy. The buttons on the toolbar are enabled or disabled
depending upon the item you have selected. The different icons are described below.
Table 3-2 Policy Set Toolbar
OperationDescription
Edit the policy Launches the Policy Builder.
Create or add a new policy to the Policy Set Launches the Add Policy Wizard.
Remove and delete the selected policy Deletes the policy from the project.
Remove the selected policy from the Policy Set,
but do not delete it
Move the policy up the policy chainMoves the policy up in the processing order.
Move the policy down the policy chain Moves the policy down in the processing order.
Removes the policy from the selected policy set
object but doesn’t delete the policy.
Keyboard Support
You can move through the policy set with keystrokes as well as using the mouse. The supported
keystrokes are listed below.
Managing Policies with the Policy Builder25
Table 3-3 Keyboard Support
KeystrokeDescription
Up-arrowMoves the selected policy up in the processing
order.
Down-arrowMoves the selected policy down in the processing
order.
DeleteDeletes the policy from the project.
MinusRemoves the policy from the selected policy set,
but does not delete it.
PlusLaunches the Add Policy Wizard.
Ctrl+ZUndoes the last operation.
Ctrl+YRedoes the last operation.
3.3.3 Using the Add Policy Wizard
novdocx (en) 13 May 2009
The Add Policy Wizard launches when you click the Create or add a new policy to the Policy Set
icon in the toolbar. The Add Policy Wizard enables you to do the following:
“Creating a Policy” on page 26
“Copying a Policy” on page 27
“Linking to a Policy” on page 28
To launch the Add Policy Wizard:
1 Select a driver in the Outline view.
2 Select a policy set item in the policy set, then click Create or add a new policy to the Policy Set
.
Creating a Policy
1 In the Add Policy Wizard, select Create a new policy, then click Next.
You can also add a policy by right-clicking a policy set in the Policy Flow view, selecting Add
Policy, then selecting how to create the policy:
DirXML Script
XSLT
Link To Existing
Copy Existing
Schema Map (Only displayed, if the Schema Map policy set is selected.)
2 In the Create Policy dialog box, specify a policy name, then click Next.
Select Open Editor after creating object to automatically launch the Policy Builder after
creating the new policy.
26Policies in Designer 3.5
Accept the default container, or browse to and select the Driver, Publisher, or Subscriber object
where you want the policy to be created.
If a policy is not reused by multiple drivers, you typically create that policy under the driver or
channel that is using it.
This decision depends on how you want to organize the policies. By default, policies are placed
under the container object that is selected in the Outline tab when the Add Policy Wizard is
launched.
For example, if you move to a Publisher object in the Outline tab and then add a policy to a
policy set, the policy defaults to the Publisher container.
novdocx (en) 13 May 2009
You can change this setting if you want to create policies in a different container. For example,
you can set up a policy library, put all of the common policies under this driver, and then simply
reference the policies from the other drivers. That way, the policy is common. If you need to
change a policy, you need to do it only once.
3 In the Select Type dialog box, select the type of policy you want to implement, then click
Finish.
The policy type defaults to DirXML Script. You can select XSLT, if you don’t want to use
®
DirXML
Script.
If you create a Schema Map policy set, an additional option is available for Schema Map.
The new policy appears in the expanded policy set.
Copying a Policy
1 In the Add Policy Wizard, select Copy a policy, then click Next.
2 In the Create Policy dialog box, provide the necessary policy information, then click OK.
Specify a name for the new policy
Managing Policies with the Policy Builder27
Accept the default container, or browse to and select the Driver, Publisher, or Subscriber
object where you want the policy to be created.
Browse to and select the policy you want to copy, then click Finish.
Linking to a Policy
novdocx (en) 13 May 2009
1 In the Add Policy Wizard, select Link a policy, then click Next.
2 In the Link Policy dialog box, click Browse to launch the model browser.
3 Browse to and select the Policy object you want to link into the policy set, then click OK.
Linking a policy into a policy set doesn’t create a new Policy object. Instead, it adds a reference
to an existing policy. This reference can be to any existing policy within the current Identity
Vault. It doesn’t need to be contained within the current Driver object, but the policy type must
be valid for the policy set that it is being linked to. For example, you can’t link a Schema Map
policy into an Input policy set.
Linking a policy into a policy set is not permitted when viewing all policies.
4 Click Finish to link to the selected policy.
3.4 Creating a Rule
A rule is a set of conditions that must be met before a defined action occurs. Rules are created from
condition groups, conditions, and actions.
Rules can be created in four different ways:
Section 3.4.1, “Creating a New Rule,” on page 29
Section 3.4.2, “Using Predefined Rules,” on page 31
Section 3.4.3, “Including an Existing Rule,” on page 32
Section 3.4.4, “Importing a Policy From an XML File,” on page 32
28Policies in Designer 3.5
3.4.1 Creating a New Rule
When you create a rule, you create condition groups, conditions, and actions. Each rule is composed
of conditions, actions, and arguments. For more information, click the Help icon when creating
each item. The help files contain a definition and an example of the item being used.
“Creating a Rule” on page 29
“Creating a Conditional Group” on page 30
“Creating a Condition” on page 30
“Creating an Action” on page 31
Creating a Rule
Policy Builder includes a wizard to step you through the process of creating a rule.
NOTE: On any of the wizard dialog boxes, you can click Finish to exit the wizard and create a rule
with the details you have specified to that point.
novdocx (en) 13 May 2009
1 In Policy Builder toolbar, click Rule .
2 In the Name and Describe Rule dialog box, specify the name of the rule, then click Next.
3 In the Select the Condition Structure dialog box, select the rule’s condition structure, then click
Next.
You can choose OR Conditions, AND Groups or AND Conditions, OR Groups.
4 In the Define the Condition dialog box, select the condition you want, specify the appropriate
information, then click Next.
The icons next to the Name field let you browse the Identity Vault schema, the connected
application schema, or use the Variable Selector to select the appropriate information.
5 In the Continue Defining Conditions dialog box, select the appropriate option, then click Next.
If desired, you can define additional conditions or condition groups before proceeding. For this
example, there is only one condition.
Managing Policies with the Policy Builder29
6 In the Define the Action dialog box, select the action that you want, then click Next.
7 In the Continue Defining Actions dialog box, select the appropriate option, then click Next.
If desired, you can define additional actions before proceeding. For this example, there is only
one action.
8 In the Summary page, click Finish to create the rule.
You can expand or collapse the view of the rule by clicking the plus or minus sign.
novdocx (en) 13 May 2009
Creating a Conditional Group
1 In the Policy Builder, right-click the Conditions tab then click Append Condition Group.
You can also right-click the name of the Condition Group, then click New > Insert Condition
Group Before or Insert Condition Group After.
Change the condition for the Condition Groups by clicking the And/Or icon.
Creating a Condition
1 Right-click the condition, then click New > Insert Condition Before or Insert Condition After.
30Policies in Designer 3.5
Loading...
+ 480 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.