Caught Exception at Azure AD Driver Initialization

Identity Manager Azure Active Directory Driver - Caught Exception during Initialization


Situation


The following error is received when attempting to start the Azure AD driver.

DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD_Azure: RESTSubscriptionShim.init()
DirXML: [11/30/18 11:46:33.46]: TRACE:  Azure AD: Caught exception during REST Channels initialization.
DirXML: [11/30/18 11:46:33.46]: TRACE:  Remote Loader: PublicationShim.init() returned:
DirXML: [11/30/18 11:46:33.46]: TRACE:  <nds dtdversion="4.x" ndsversion="8.x">
    <source>
        <product build="20171120_1044" instance="Azure AD" version="5.0.1.2">Identity Manager Driver for Azure AD and Office 365</product>
        <contact>NetIQ Corporation</contact>
    </source>
    <output>
        <status level="fatal" type="com.novell.nds.dirxml.driver.azure.StatusException"/>
    </output>
</nds>
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Publisher
    Level   = fatal
DirXML: [11/30/18 11:46:33.46]: 
DirXML Log Event -------------------
    Driver  = \VAULT\novell\services\DriverSet\Azure AD
    Thread  = Subscriber
    Level   = error
    Message = Fatal error returned from shim

Environment


  • Identity Manager Driver - Azure Active Directory version 5.0.1.2
  • Identity Manager 4.8.0


Resolution


The Application User password being used by the Identity Manager Azure Active Directory driver to authenticate into Azure Active Directory contained a special character in the password.   In this case a < character.


After removing the special character from the password, and saving the new application password for the application user on the driver properties, the driver was able to start successfully.

Deprecation for IDM Driver for Office365

Deprecation and migration plan for NetIQ Identity Manager Driver for Office 365


Micro Focus is deprecating the Office 365 driver for NetIQ Identity Manager. This driver has been superseded by the Azure AD driver, which is available at no extra cost to all Office 365 driver customers.

The Office 365 driver was developed at a time when Microsoft did not offer a comprehensive set of APIs to access Office 365. As the Azure platform evolved, Microsoft updated its API set to provide efficient and secure access to the platform. In response, Micro Focus developed the Azure Active Directory Driver: a faster, more scalable, and more secure driver that supports both Azure AD and Office 365.

Micro Focus have continued to support the older Office 365 driver to allow customers sufficient time for migration to the new Azure AD driver. However, Microsoft has announced that they are deprecating some of the underlying technology, which will make the driver non-functional in some scenarios.

As a result, Micro Focus are urging all Office 365 driver customers to migrate to the new Azure AD driver as soon as possible.