AzureAD Connector throws a NullPointerException
IDM 4.7.1 Remote Loader
AzureAD Connector: 188.8.131.52
REST Connector: 184.108.40.206
I just started with the AzureAD Connector, and it runs fine when I do not enable the Exhange portion. When that bit is enabled, the SHIM gives back a NullPointerException.
DirXML: [08/14/19 09:28:05.68]: TRACE: Azure-AD: Total 0 schema extensions are registered for application a36221cf-8d91-4b5c-8f76-7624346f567e
DirXML: [08/14/19 09:28:05.68]: TRACE: Azure-AD: Populating 0 registered schema extensions in driver schema.
DirXML: [08/14/19 09:28:05.68]: TRACE: Azure-AD: Caught exception during REST Channels initialization.
DirXML: [08/14/19 09:28:05.68]: TRACE: Azure-AD: java.lang.NullPointerException
DirXML: [08/14/19 09:28:05.68]: TRACE: Remote Loader: PublicationShim.init() returned:
DirXML: [08/14/19 09:28:05.68]: TRACE:
<product build="20190328_1251" instance="Azure-AD" version="220.127.116.11">Identity Manager Driver for Azure AD and Office 365</product>
<status level="fatal" type="com.novell.nds.dirxml.driver.azure.StatusException"/>
Has anyone seen this before? I have going through all the configuration setups, and the WEB service (for Exchange) is working like a champ.
No Casper, there has been no response.
It would appear that nobody has ever come across this issue. There was another thread that I commented on, but that has not been answered either. It would be nice if the developers of the SHIM would give some insight.
At the very least, if anyone (and I mean anyone) has got this to work, can they please share a screenshot of the permissions that they have granted in the Azure portal?
The Driver document, at least for the new Azure Portal, does not appear to be correct.