1.3 Key Driver Features

The sections below contains a list of the key driver features.

1.3.1 Local Platforms

The SOAP driver can be installed locally on the following platforms:

  • NetWare® 6 or 6.5 with the latest Support Pack

  • Novell® Open Enterprise Server with the latest Support Pack

  • Windows* NT*, 2000, or 2003 with the latest Service Patch

  • Linux Red Hat* AS, ES 2.1, or AS 3.0

  • SUSE® Linux Enterprise Server 8, 9 (including SP1), or 10

  • Solaris* 8 or 9

  • AIX* 5.2L

1.3.2 Remote Platforms

The SOAP driver can use the Remote Loader service. The Remote Loader service for the SOAP driver can be installed on the following platforms:

  • Novell Open Enterprise Server with the latest Support Pack

  • Windows NT, 2000, or 2003 with the latest Service Patch

  • Linux Red Hat AS, ES 2.1, or AS 3.0

  • SUSE LINUX Enterprise Server 8, 9 (including SP1), or 10

  • Solaris 8 or 9

  • AIX 5.2L

For more information about installing the Remote Loader services, see Installing the Remote Loader in the Novell Identity Manager 3.5.1 Administration Guide .

1.3.3 Role-Based Entitlements

The SOAP driver does not have Role-Based entitlement functionality defined with the example configuration files. The driver does support entitlements, if there are policies created for the driver to consume.

1.3.4 Password Synchronization Support

The example configuration files for the SOAP driver are capable of synchronizing passwords.

1.3.5 Information Synchronized

Unlike most other drivers, the SOAP driver synchronizes protocols instead of objects. It synchronizes the SPML 1.0 and DSML 2.0 protocols. The driver contains the following features:

  • HTTP transport of data between the Identity Vault and a Web service

  • Example configurations for SPML and DSML

  • Customization of HTTP Request-Header fields

    By default, a basic authorization request header with an ID and password is provided for the Subscriber channel. For more information, see Section 4.1, Creating a Driver Object by Using a Driver Configuration File.

  • SSL connections using the HTTPS protocol

  • Subscriber HTTP and HTTPS proxy servers

  • Definition and selection of multiple Subscriber connections in the policy at runtime

  • Potential to act as an HTTP or HTTPS listener for incoming connections on the publisher channel

  • Potential extensibility using customized Java* code

    For more information, see Section A.0, Using Java Extensions.