Novell Credential Provisioning for Identity Manager 4.0.1 enhances the user provisioning abilities of any Identity Manager driver by providing the capability to simultaneously provision application credentials to the Novell SecretStore and Novell SecureLogin credential repositories. Additionally, you can provision the SecureLogin passphrase question and answer in environments where non-repudiation is desired.
These features enhance the user Single Sign-On experience and increase the return on investment of Single Sign-On technologies by eliminating the initial setup of SecureLogin account information, providing additional security to application credentials, and reducing the replication of effort normally associated with provisioning Single Sign-On credential stores for users. In addition, the Credential Provisioning can use Identity Manager policies to automatically de-provision application credentials to prevent access to application data.
This guide provides a detailed reference of how to implement Credential Provisioning with SecureLogin and SecretStore. The guide does not contain configuration information for Identity Manager, SecureLogin, or SecretStore.
This guide is intended for Identity Manager administrators.
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.
For the most recent version of this document, visit the Identity Manager Web site.
For documentation on Identity Manager, see the Identity Manager 4.0.1 Documentation Web site .
For documentation on Identity Manager drivers, see the Identity Manager 4.0.1 Documentation Web site .
For documentation on SecureLogin, see the Novell SecureLogin 6.1 Documentation Web site .
For documentation on SecretStore, see the Novell SecretStore 3.4 Documentation Web site .
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.