Azure Active Directory Driver 5.1.70100 Readme

The Azure Active Directory Driver also referred to as Azure AD Driver in this document, allows you to seamlessly provision and deprovision users, group memberships, exchange mailboxes, roles, Teams, Channels, SKU and licenses to Azure AD Cloud. You can also configure the driver to integrate with Identity Manager Service for Exchange Online (Identity Manager Exchange Service) for synchronizing Office 365 attributes.

This Readme comprises the following sections:

Overview

This update is applicable for an Identity Manager Driver for Office 365 and Azure Active Directory running Identity Manager 4.8.x. The driver version will be changed to 5.1.70100 after the patch is applied.

Note:

System Requirements

Prerequisites

Run the following commands before upgrading the driver to install the requirments:

Upgrading the Driver

The driver upgrade process involves the following tasks:

  • To upgrade the driver files, refer to: Upgrading the Driver Files
  • To set the delegated and application permissions, refer to:Azure AD Directory Configuration Changes - refer to Step3 in the implementation Guide
  • To set up SSL between the driver and Azure AD graph REST endpoints, refer to: Secured Communication with Microsoft Graph
  • To set up SSL between the driver and Identity Manager Exchange Service, refer to: Securing Communication with Identity Manager Exchange Service

    • 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_AzureAD_5.1.7_P1.zip file to a temporary location on your computer.

    5. (Conditional) To upgrade the driver files:




    6. As a non-root user, perform the following steps:

      1. Verify that /rpm directory exists and contains _db.* file.

        2. The _db.* file is created during a non-root installation of the Identity Manager engine. The absence of this file might indicate that the Identity Manager is not installed properly. You must reinstall the 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:

        3. 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:

        4. 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-DXMLRESTAzure.rpm

        where /opt/novell/eDirectory is the location where non-root eDirectory is installed and /home/user/ is the home directory of the non-root user.

    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.

    Known Issue

    Memory leak issue in IDMExchange service.

    Issue:

    In IDMExchange service we have observed Memory leak issue which is caused due to Microsoft cmdlets. In Microsoft documentation it is mentioned that "Frequent use of the Connect-ExchangeOnline and Disconnect-ExchangeOnline cmdlets in a single PowerShell session or script might lead to a memory leak. The best way to avoid this issue is to use the CommandName parameter on the Connect-ExchangeOnline cmdlet to limit the cmdlets that are used in the session.".

    Workaround:

    Restart IDMExchange Service when you see noticeable increase in memory.

    Technical Support Information

    Issues Fixed in current Release (5.1.70100)

    Issues Fixed in Previous Release (5.1.7)