IDCS Group Lookup Reconciliation Schedule Job Throwing java.lang.NullPointerException
(Doc ID 2431475.1)
Last updated on SEPTEMBER 27, 2023
Applies to:
Identity Cloud Service (IDCS) - Version N/A and laterInformation in this document applies to any platform.
Symptoms
Customer has integrated Oracle Identity Manager (OIM) with Oracle Identity Cloud Services (IDCS).
On running the IDCS Group Lookup Reconciliation Schedule Job the job fails with the following Null Pointer Exception (NPE):
[2018-07-16T11:29:54.960-03:00] [servername] [ERROR] [] [ORG.IDENTITYCONNECTORS.RESTCOMMON.UTILS.RESTCOMMONUTILS] [tid: tid] [userId: oiminternal] [ecid: ECID] [APP: oim#11.1.2.0.0] org.identityconnectors.restcommon.utils.RESTCommonUtils : checkStatus : Description not available for received status code.302
[2018-07-16T11:29:54.962-03:00] [servername] [ERROR] [] [ORG.IDENTITYCONNECTORS.FRAMEWORK.IMPL.API.LOCAL.OPERATIONS.CONNECTORAPIOPERATIONRUNNERPROXY] [tid: tid] [userId: oiminternal] [ecid: ECID] [APP: oim#11.1.2.0.0] org.identityconnectors.framework.impl.api.local.operations.ConnectorAPIOperationRunnerProxy : invoke : null[[
java.lang.NullPointerException
at org.identityconnectors.genericscim.GenericSCIMConnector.dispose(GenericSCIMConnector.java:273)
at org.identityconnectors.framework.impl.api.local.operations.ConnectorAPIOperationRunnerProxy.invoke(ConnectorAPIOperationRunnerProxy.java:125)
at com.sun.proxy.$Proxy497.search(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.identityconnectors.framework.impl.api.local.operations.ThreadClassLoaderManagerProxy.invoke(ThreadClassLoaderManagerProxy.java:107)
at com.sun.proxy.$Proxy497.search(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.identityconnectors.framework.impl.api.BufferedResultsProxy$BufferedResultsHandler.run(BufferedResultsProxy.java:162)
If we look at the above log we can see before the Null Pointer Exception (NPE) the following error:
checkStatus : Description not available for received status code.302
To get more information we need to set the connector in trace:32 mode following the steps in the documentation that can be found here https://docs.oracle.com/cd/E22999_01/doc.111/e71438/GUID-2E4BD7FB-599F-4442-98E0-672AB871B07A.htm#GUID-7F3EC1A0-88B0-42F8-A1EB-333C4B1F3022
After enabling the connector on trace:32 mode running the schedule job shows the following:
...
INFO: org.identityconnectors.restcommon.ClientHandler : executeRequest : Making a 'POST' call using the URL 'https://myservices-url.console.oraclecloud.com/mycloud/cloudportal/dashboard'
INFO: org.identityconnectors.restcommon.utils.RESTCommonUtils : checkStatus : REST call Status : HTTP/1.1 302 Moved Temporarily
The IDCS connector is a REST connector and as such before performing anything it tries to get a valid token to access IDCS.
From the above logs we can clearly see that we are not trying to reach a token endpoint but instead the myservices login page that redirects us to the IDCS login page (HTTP code 302)
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |