1.3.1 Local Platforms

A local installation is an installation of the driver on the Metadirectory server. The Sungard Banner driver can be installed on the operating systems supported for the Metadirectory server.

For information about the operating systems supported for the Metadirectory server, see Metadirectory Server in System Requirements in the Identity Manager 4.0 Framework Installation Guide.

1.3.2 Remote Platforms

The Sungard Banner driver can use the Remote Loader service to run on a server other than the Metadirectory server. The Sungard Banner driver can be installed on the operating systems supported for the Remote Loader.

For information about the supported operating systems, see Remote Loader in System Requirements in the Identity Manager 4.0 Framework Installation Guide.

1.3.3 Supported Operations

The Sungard Banner driver interacts with Banner via Banner Enterprise Identity Services (BEIS). BEIS publishes data in SPML format. The driver is limited to operations supporteed by SPML. The basic configuration files for the Sungard Banner driver are capable of performing the following operations on User objects:

BEIS does not support rename or move operations. It is possible to synthesize these operations in an Identity Manager Policy based on attribute data changes in the XML data received from BEIS.

The driver publishes role information from the Sungard system. Roles are used to grant access to information on the Sungard Portal in Luminis and other Sungard applications and resources. Sungard does not delete identities after they are created. The Sungard system removes roles from the collection of roles on a given user. Consultants or Identity Manager administrators deploying the driver might implement Role-Based Entitlements on other drivers to react to changes in the list of roles for a given user.

For additional information, see Section 3.1.7, Understanding Institutional Roles.

1.3.4 Password Synchronization Support

By default, the Novell Identity Manager driver for Sungard Banner policies do not synchronize passwords to or from the Sungard system. However, when a user is added to the Identity Vault, a password can be created for the user by selecting an attribute to pull the password from, or by generating a random password through a policy on the Publisher Channel Command Transform.

To configure this policy, set the Banner Password Settings attributes on the Password Settings tab of the GCV editor.

Select Random Password to have a random password generated for the new user. You can specify the number of alphabetic characters and numeric characters that must be used in generating the password.

Select Attribute Value from User to have a password value set from the value of an attribute on the user object. BEIS can be configured to publish a password from the Banner system as an extension attribute. The driver recognizes the extension attribute and publish it as an <add-attr> element in the XDS document to be sent to the Metadirectory engine. Map the Banner element name to an eDirectory attribute and set that attribute name as the eDirectory attribute to use for initial password value to have the driver password policy use the attribute in the specified eDirectory attribute as the user’s new password.