Policies in iManager for Identity Manager 4.0.1

Novell Identity Manager 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.

iManager does not support packages, which deliver Identity Manager content. If you change policies or package content in iManager, it breaks the package management capabilities in Designer. You can use iManager to start and stop drivers, check the driver health, or activate drivers. For more information, see Managing the Identity Manager Content in the Designer 4.0.1 for Identity Manager 4.0.1 Administration Guide.

This guide provides detailed information on creating and managing policies in iManager.

Audience

This guide is intended for Identity Manager administrators.

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 iManager, visit the Identity Manager Documentation Web site.

Additional Documentation

For documentation on Identity Manager drivers, see the Identity Manager Documentation Web site .

For documentation on Novell iManager, see the Novell iManager Documentation Web site.

For documentation on Designer see, the Designer 4.0.1 for Identity Manager 4.0 Administration Guide.

Documentation Conventions

In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

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.