Identity Vault – Unable to connect to Linux/Unix Remote Loader Driver
Checklist for solving error (-9006) Detail from driver
The Linux/Unix driver uses embedded Remote Loader Technology to communicate with the Identity Vault — bi-directionally synchronizing changes between the Identity Vault and the connected system.
New comers to Identity Manager commonly come face-to-face the above error.
The checklist below will save hours upon hours of undesired debugging efforts
1.Ensure the Remote Loader is installed/initiated on the Linux/Unix system
Type “rdxml” in the command line.
If the command is NOT recognized, install the Remote Loader from here.
2.Start the Remote Loader
Starting the Linux/Unix driver (from iManager or designer) is one thing, starting the Remote Loader driver is another:
On a terminal, type “rdxml -config <path_to_config file> -sp remote_loader_<password> driver_<password>” to define driver and remote loader passwords
Then type “rdxml -config <path_to_config_file>” to start the driver
You can check the status with “/etc/init.d/rdxml status” to confirm that the remote loader driver is running
If upon starting the driver you get the below error message, resolve this by running “nxdrv-config” from the command line, and following the prompts to set the passwords
“remote loader password and driver object password must be set”
3. Ensure that the Remote Loader/Driver object password(s) you specify for the Remote Loader driver are the same with those on the Linux/Unix driver configuration.
If you make any changes to the Linux/Unix driver configuration from designer, don’t forget to deploy those changes
4. Examine the Status Log and DSTRACE output of the Linux/Unix driver and the Remote Loader Driver.
You might want to edit the trace levels (to “3” for instance) to get more detailed debugging information
You can edit the trace level for the Linux/Unix driver from the setting at “/etc/nxdrv.conf”
For the Remote Loader driver, you can edit the trace level in the created configuration file
5. If you have selected to use an SSL connection in the Linux/Unix driver configuration (recommended), make sure you configure the Remote Loader driver for SSL as well
If you don’t, you’ll get the following error in the Remote Loader driver’s trace file:
“Unable to establish client connect; make sure certificates match”
6. Ensure the connection parameters (hostname, port, KMO, etc…) in the Remote Loader configuration file that you created matches the Remote Loader authentication settings in the Linux/Unix driver configuration
Questions, comments or concerns? Feel free to reach out to us below or at IDMWORKS