Environment
Identity Manager 4.6
Identity Manager Driver - Office 365 and Azure Active Directory
Situation
Trace of the remote loader shows:
DirXML: [04/19/18 13:21:20.86]: TRACE: <nds dtdversion="3.0">
<source>
<product build="20150722_0750" version="1.0.0.0">Identity Manager REST Driver</product>
<contact>NetIQ Corporation.</contact>
</source>
<output>
<status level="success" type="driver-general">
<driver-operation-data class-name="users" command="schema-extensions" dest-dn="">
<response method="GET" url="https://graph.windows.net/siteconnectioninfo.onmicrosoft.com/applications/6cf8fa02-980a-449e-837c-fcc2a9b9dacf/extensionProperties?api-version=1.6">
<url-token/>
<header/>
<value>{"odata.metadata":"https://graph.windows.net/siteconnectioninfo.onmicrosoft.com/$metadata#directoryObjects/Microsoft.DirectoryServices.ExtensionProperty","value":[]}</value>
</response>
</driver-operation-data>
</status>
</output>
</nds>
DirXML: [04/19/18 13:21:20.86]: TRACE: Azure AD: Caught exception during REST Channels initialization.
DirXML: [04/19/18 13:21:20.86]: TRACE: Remote Loader: DriverShim.getSchema() returned:
DirXML: [04/19/18 13:21:20.86]: 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">Graph: OData Error has occured. Details: null-null</status>
</output>
</nds>
DirXML: [04/19/18 13:21:20.86]:
DirXML Log Event -------------------
Driver = \VAULT-TEST\vault\services\DriverSet\Azure AD
Thread = Subscriber
Level = fatal
Message = Graph: OData Error has occured. Details: null-null
Resolution
Apply the current updated to the Rest Driver to the remote loader server (or locally) where the driver is running.
Along with the current Rest Driver, verify that you have met the driver pre-requisites per section 2.1.1 Prerequisites for Driver in the NetIQ Office 365 and Azure Active Directory Driver Implementation Guide.
If you are running a remote loader, the corresponding jar files installed with the IDM version you installed the remote loader from can affect the driver startup. In this particular issue, several other jar files were out of date as well.
-----------Snipit from the documentation---------
Before installing the driver files, perform the following actions in the Identity Manager installation directory in one of the following locations:
Linux: /opt/novell/eDirectory/lib/dirxml/classes
Windows: C:\Novell\IdentityManager\NDS\lib
Delete the j2eevalidate.jar.
Back up the commons-codec-1.3.jar file.
Delete all versions of httpclient.jar and httpcore.jar files except the following files:
httpclient-4.4.1.jar
httpcore-4.4.1.jar
Replace commons-codec-1.3.jar with commons-codec-1.6.jar.
The commons-codec-1.6.jar is located in the lib folder of the NIdM_Driver_4.5_O365_AzureAD.zip file.
Restart eDirectory.