1.3 Requirements

The system requirements for driver components are described in the following sections. Identity Manager Fan-Out driver components do not require the systems they run on to be dedicated solely to them.

Topics in this section include

1.3.1 User Rights Requirements

The installation and configuration of the driver require a user with full administrative rights and privileges in eDirectory and on the target systems. You can grant more limited rights to other users to use the Fan-Out driver Web interface for administrative functions. For details of rights needed for administrative functions, see Section 3.4.1, Rights Required for Web Interface Use.

1.3.2 Secure Sockets Layer Entropy Requirements for UNIX Systems

Secure Sockets Layer (SSL), used for secure communication between components, requires a source of entropy. Some UNIX implementations provide a /dev/random device for entropy. If your UNIX implementation does not include a /dev/random device, you must install an entropy daemon. You must also include an Entropy configuration parameter in your core driver configuration to specify the source of entropy. For more information about the Entropy parameter, see System Entropy Source.

Solaris versions before Solaris 9 do not include a /dev/random device. Sun* has released this functionality for versions 2.6 onward in Patch ID 112438-01.

1.3.3 Password Replication Requirements

If you use password replication, you must ensure that the driver is notified of changes to passwords.

  • If your eDirectory is configured to fully support Universal Password, the driver is notified of password changes in eDirectory.

  • If you do not use Universal Password, you must install and configure the appropriate password intercepts.

    • You must install the Novell Client Password Intercept on each Windows* workstation that uses eDirectory. This intercept is distributed in the intercepts\client32 directory of the distribution media.

    • You must install and run the NetWare® Password Intercept on all NetWare servers that run applications that use the eDirectory application programming interface (API) to change passwords in eDirectory. This intercept is distributed in the intercepts\netware directory of the distribution media.

  • The OS/400 Password Validation Program Exit provides password change information from OS/400 platforms.

For information about installing and configuring the password intercepts, see the administration guide and the appropriate Quick Start for your platform operating system type.

1.3.4 Core Driver Requirements

  • Novell Identity Manager.

  • Novell eDirectory versions supported by the Identity Manager version in use.

  • One of the following OS platforms, in a version supported by the Identity Manager and eDirectory version in use:

    • NetWare

    • Windows

    • Linux*

    • Solaris

  • TCP/IP network connectivity.

  • A writable replica of the partition that holds the ASAM System container must reside on the LDAP host server used by the core driver.

  • Replicas (full or filtered) of objects covered by a Census Search object (primary core driver only).

    The Fan-Out driver is configured for the attributes in the following lists. If you use filtered replicas, include the attributes shown in the following lists. If you add other attributes to the Subscriber filter, you must ensure that they are also available in your filtered replicas.

    Alias Attributes

    • Aliased Object Name

    • CN

    • GUID

    User Attributes

    • CN

    • Group Membership

    • GUID

    • Login Disabled

    • Surname

    ASAM-enterpriseUser Attributes

    • ASAM-addTime

    • GUID

    Group Attributes

    • CN

    • GUID

    • Member

    Organizational Role Attributes

    • CN

    • GUID

    • Role Occupant

HINT:iManager provides a wizard for setting up filtered replicas.

1.3.5 Requirements for Workstations Used for Installation and Administration

The workstations used to install, configure, and administer the driver must meet the following requirements.

  • TCP/IP network connectivity.

  • The ability to run iManager.

  • Connectivity to the tree to be managed by the driver.

  • If the installation computer runs UNIX, gzip and tar utilities.

  • Connectivity to the file system of the computer that is to receive components being installed. If the installation computer is not the same as the target host, a drive must be mapped to the target host.

1.3.6 Platform Services Requirements

For a list of supported Platform Services operating systems and version requirements, see the Concepts and Facilities Guide.