Ensure that you use a version of Identity Console that is compatible with your version of Identity Manager.
To set up certificates, the driver shim communicates with the Metadirectory server using the LDAP secure port (636).
Ensure that eDirectory™ is running LDAP with SSL enabled. For details about configuring eDirectory, see the OpenText eDirectory Administration Guide.
Ensure that the connected system has network connectivity to the Metadirectory server.
To configure the certificate, use the I5OSDRV menu. For more information about the menu, see Using the I5OSDRV Menu.
If you cannot configure SSL using LDAP, you can install the certificate manually.
Click Certificate Management > Trusted Root Management options from the Identity Console landing page. The Trusted Root Container check box will be selected by default. Select the Trusted Root check box.
Select the appropriate trusted root certificate from the list and click the export icon.
In the next screen, do not select the check box for Export Private key.
Select Base64 format, then click OK.
Use FTP or another method to store the file on the connected system in the driver IFS path as keys/ca.pem.
If you installed the driver using the default driver IFS path, store the file as /usr/local/i5osdrv/keys/ca.pem.
Examine the status log and DSTRACE output.
The driver must be specified as a Remote Loader driver. You can set this option in Identity Console.
You must activate both Identity Manager and the driver within 90 days. The Drivers page in Identity Console shows when Identity Manager requires activation. The Driver Overview page shows when the driver requires activation.
For details about activating OpenText Identity Manager Products, see the Identity Manager Installation Guide on the Identity Manager 4.10 Documentation Web site .
For more information about troubleshooting Identity Manager engine errors, see the Identity Manager 4.10 Documentation Web site.
Examine the trace file.
Apply all patches for your operating system.
Ensure that the Remote Loader and Driver object passwords that you specified while setting up the driver on the Metadirectory server match the passwords stored with the driver shim.
The passwords are stored in the driver IFS path in the keys directory in encrypted files dpwdlf40 (Driver object password) and lpwdlf40 (Remote Loader password).
To update these passwords on the connected system, use the I5OSDRV menu. For more information about the menu, see Using the I5OSDRV Menu.
To update these passwords on the Metadirectory server, use Identity Console to update the driver configuration. For details, see Driver Configuration Page.
Ensure that the correct host name and port number of the connected system are specified in the Driver Configuration Remote Loader connection parameters. You can change the port number (default 8090) in the driver shim configuration file.
Examine the status log, DSTRACE output, trace file, and job log.
To be provisioned, users and groups must be in the appropriate base container. You can view and change the base containers in Identity Console on the Global Config Values page of the Drivers module. For more details, see Global Configuration Values Page.
To provision identities from the Identity Vault to the connected system, the driver Data Flow property must be set to Bidirectional or Identity Vault to Application. To change this value, re-import the driver rules file over your existing driver.
The user that the driver is security equivalent to must have rights to read information from the base container. For details about the rights required, see Table 2-2, Base Container Rights Required by the Driver Security-Equivalent User.
Examine the status log, DSTRACE output, and trace file.
Examine the User Base Container and Group Base Container GCV values. For more details, see Global Configuration Values Page.
To provision identities from the connected system to the Identity Vault, the driver Data Flow property must be set to Bidirectional or Application to Identity Vault. To change this value, re-import the driver rules file over your existing driver.
The user that the driver is security equivalent to must have rights to update the base container. For details about the rights required, see Table 2-2, Base Container Rights Required by the Driver Security-Equivalent User.
Examine the status log, DSTRACE output, and job log.
There are several password management properties available in Identity Console on the Global Config Values page of the Drivers module. Ensure that the connected system accepts passwords from the Identity Vault. To determine the right settings for your environment, view the help for the options, or see the Administration Guide on the Identity Manager 4.10 Documentation Web site.
Ensure that the user’s container has an assigned Universal Password policy and that the Synchronize Distribution Password When Setting Universal Password option is set for this policy.
Examine the status log, DSTRACE output, and the trace file.
Ensure that the The Identity Vault Accepts Passwords from the i5/OS Connected System GCV is set.
To publish password change information, you must change passwords with a method that uses the Validate Password exit program. The driver obtains password change information from this exit. Administrative password resets must be performed in the Identity Vault.
If the Require Password Policy Validation before Publishing Password GCV is set, the user’s password must satisfy the password rules in the password policy assigned to the user container.
Examine the status log, DSTRACE output, trace file, and job log.
Examine the driver Data Flow setting to verify the authoritative source for identities.
Identity Vault and connected system identities must be associated before events are synchronized. To view an identity’s associations, use the Object Inspector page in Identity Console and search for the object. You can migrate identities to establish associations. For details, see Migrating Identities.
Renaming profiles is not supported by i5/OS. The driver can optionally process rename commands by deleting and recreating a profile with identical attributes and the new name. Before using this functionality, please review the CL *PGM source found in rename.cl, renuser.cl, rengroup.cl and make sure it meets the requirements of your environment. For details, see The Scriptable Framework. To enable rename processing, disable the Veto Rename Events policy in the Event Transformation.
Identity Vault move events can remove the identity from the base container monitored by the driver to a container that is not monitored by the driver. This makes the move appear to be a delete.