REST Driver 1.1.2.0300 Readme

This Readme comprises the following sections:

• Overview
• System Requirements
• Upgrading the Driver
• Technical Support Information

Overview

This update is applicable for REST drivers running Identity Manager 4.8.x, or later. The driver version will be changed to 1.1.2.0300 after the patch is applied.

System Requirements

Upgrading the Driver

The driver upgrade process involves the following tasks:

• Upgrading the Driver Packages
• Upgrading the Driver Files

Upgrading the Driver Packages

Note: No new packages have been shipped as part of this release.

Upgrading the Driver Files

1. Take a back-up of the current driver configuration.


2. (Conditional) If the driver is running locally, stop the driver instance and the Identity Vault.


3. (Conditional) If the driver is running with a Remote Loader instance, stop the driver and the Remote Loader instance.


4. Download and unzip the contents of the IDM_REST_1.1.2_P3.zip file to a temporary location on your computer.


5. (Conditional) To update the driver files as a root user:


• For Identity Manager 4.8.x version:
  
  
  1. On the server where you want apply the driver patch, log in as root.
  
  
  2. Navigate to the extracted <IDM_REST_1.1.2_P3.zip> directory and perform one of the following actions for your platform:
  
  
  • Linux: Install the new netiq-DXMLRESTDrv.rpm in your driver installation directory by running one of the following command in a terminal window:
  
  
  • If you are upgrading the patch, run the following command:

  rpm -Uvh (patch-path)/linux/netiq-DXMLRESTDrv.rpm

  • Windows: Copy the RESTCommon.jar, RESTDriverShim.jar, RESTUtil.jar files to your driver installation folder. For example, \NetIQ\IdentityManager\NDS (local installation) or \Novell\RemoteLoader\64bit (remote installation).
  3. Restart eDirectory or Remote Loader (RL) Instance


6. (Conditional) To update the driver files as a non-root user:


1. Verify that <non-root edirectory="" location="">/rpm directory exists and contains _db.* file.

The _db.* file is created during a non-root installation of the Identity Manager engine. Absence of this file might indicate that Identity Manager is not properly installed. Reinstall Identity Manager to correctly place the file in the directory.

2. To set the root directory to the location of non-root Identity Vault, enter the following command in the command prompt:

ROOTDIR=<non-root eDirectory location>

This will set the environmental variables to the directory where Identity Vault is installed as a non-root user.

3. To install the driver files, enter the following command:

For example, to install the REST driver RPM, use this command:

rpm --dbpath $ROOTDIR/rpm -Uvh --relocate=/usr=$ROOTDIR/opt/novell/eDirectory --relocate=/etc=$ROOTDIR/etc --relocate=/opt/novell/eDirectory=$ROOTDIR/opt/novell/eDirectory --relocate=/opt/novell/dirxml=$ROOTDIR/opt/novell/dirxml --relocate=/var=$ROOTDIR/var --badreloc --nodeps --replacefiles /home/user/netiq-DXMLRESTDrv.rpm

7. (Conditional) If the driver is running locally, start the Identity Vault and the driver instance.


8. (Conditional) If the driver is running with a Remote Loader instance, start the Remote Loader instance and the driver instance.

Technical Support Information

Security Fix

• CVE-2022-26322

• ALM 230938 - When 204 (No content) is returned from a POST this is interpreted as an error by the REST driver.
• ALM 283077 - Custom headers in the REST Driver 1.1.1.0 are not implemented when Anonymous login method is selected.
• ALM 292115 - REST driver returns the status from two operations into one status.
• ALM 295151 - REST Driver OAuth JWT issues.
• ALM 297135 - REST Driver login failure via JWT to GSuite.
• ALM 329083 - Java Exception when executing a DELETE command via REST Driver (the Driver crashes)

• ALM 328139 - REST Driver sends a response for only one <request> when multiple <request> are sent under the <driver-operation-data> to AWS.

• This version of the driver supports an upgraded version of the jetty-all-9.4.34.v20201102-uber.jar file.

Issues Fixed in Release (1.1.2.0)

• ALM 231647 - REST shim version 1.1.0.0 breaks processing of binary content types.
• ALM 235207 - REST shim is unable to access the HTTP response headers.
• ALM 280236 - REST driver shim must retry when the "java.net.SocketTimeoutException: Read timed out" error occurs.

• Enhanced OAuth2.0 authentication with JWT Token, Refresh Token, and Bearer Token authorization.
• Important Internal Security Bug Fixes.

• Bug 1115879 - The log is enhanced to trace the OAUTH connection string for the resource types in Level 6 and Level 7.
• Bug 1160325 - The exception error for the DELETE method handler against Identity Applications REST API is not displayed anymore.
• Bug 1153678 - Enhanced the ability to handle expired JWT tokens efficiently.
• Bug 1020337 - The errors Code(-9024) for migrating users to eDirectory and error Code(-9131) for querying attribute in user is fixed.
• Bug 1156668 - REST driver now connects to an external website using the "&amp;" string instead of the "&" string which caused loading errors.
• Bug 1143750 - Multiple concurrent connections in the code is now allowed per route eliminating timeout errors.
• Bug 1139449 - The date header issue is now fixed for the date format in REST driver.
• Bug 1150240 - For basic authentication, the Identity Manager REST Driver Publisher SSL Configuration can now be set with different passwords for keystore and private key.
• Bug 1170892 - REST Driver 1.1 does not terminate anymore when jcce version 1.3.0 is used.
• Bug 1122150 - The exception errors caused by querying PAM 3.5 for the REST end points are now fixed.
• Bug 926506 - The domain name with the status code now appears as a response of REST API execution.

• Bug 1086171 - Ability to correctly handle the Content-Type header in the sub-execte process on the Subscriber channel.
• Bug 1094571 - The rs:jsonToXds() function returns valid XDS when an Add event contains multivalued attributes.
• Bug 1094572 - When the Publisher channel Add event contains structured JSON fields, the rs:jsonToXds() function does not drop the event.
• Bug 1101989 - Additional logging is provided to show REST URI validation calls.
• Bug 1109231 - Ability to update Facsimile Telephone Number on the Publisher channel.

• Bug 1011865 - Package upgrade or downgrade creates duplicate GCVs or GCV instance values and deletes ECV customization.
• Bug 1035017 - Incorrect parameter description for subOauthURL.
• Bug 1025265 - java.lang.AbstractMethodError: com.novell.xml.dom.DocumentImpl.getXmlStandalone()Z java.lang.AbstractMethodError: com.novell.xml.dom.DocumentImpl.getXmlStandalone()Z error.
• Bug 1086399 - Upgrading from version 1.0.0.2 to 1.0.1.0 does not update the driver version.
• Bug 982847 - Incorrect encoding on the Subscriber channel.
• Bug 1034526 - Upgrading the driver base package does not preserve the old driver configuration values.
• Bug 1025281 - Emtpy values cause the JSON converter to crash with a null pointer exception.
• Bug 1048054 - Forces the Identiy Manager engine to an out of memory state.
• Bug 1073348 - Unable to provide direct Bearer authentication.
• Bug 961725 - Does not accept 200 and 204 on a DELETE return.