OIM OIA Integration issue: Unable to get current Data Collection Session ID

Whilst connecting OIM with OIA, you may receive an error stating that you cannot receive the 'current Data Collection Session ID'. OIM data collection scheduler has to be enabled, which by default it is, though you may be experiencing the following error whilst attempting to import the usr or application data.
April 21, 2014
OIM-11g
OIM OIA Integration issue: Unable to get current Data Collection Session ID

Whilst connecting OIM with OIA, you may receive an error stating that you cannot receive the 'current Data Collection Session ID'. OIM data collection scheduler has to be enabled, which by default it is, though you may be experiencing the following error whilst attempting to import the usr or application data.
April 21, 2014
OIA-11g

19:08:30,144 DEBUG [OimUtilityFactory] Xellerate Discovery Settings {java.naming.provider.url=t3://localhost.localdomain:14000/oim, java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}
19:08:30,144 DEBUG [OimUtilityFactory] ********** Connecting to OIM Server **********
19:08:30,227 DEBUG [OimUtilityFactory] ********** Connection successful **********
19:08:30,236 ERROR [OIMDataProviderImpl] Unable to get current Data Collection Session ID
Thor.API.Exceptions.tcAPIException: Error while getting utility Thor.API.Operations.DataCollectionOperationsIntf
at Thor.API.tcUtilityFactory.getRemoteUtility(tcUtilityFactory.java:442)
at Thor.API.tcUtilityFactory.getUtility(tcUtilityFactory.java:331)
at com.vaau.rbacx.iam.db.support.oracle.OIMDataProviderImpl.getDataCollectionAPI(OIMDataProviderImpl.java:1657)

When you receive the
********** Connection successful **********
within the rbacx.log, it's a clear indication that you OIM OIA integration configuration and that the xlconfig.xml file has been correctly modified, if required.
.
This does however only indicate that the connection can be reached to the OIM server though does not guarantee that the OIM connection can reach the OIM instance.

This issue is likely to occur when OIM and OIA are deployed on separate domains.


SOLUTION

You need to ensure the cross domain security is enabled to ensure there's a level of trust. This has to be set on both weblogic domains. You may also need to ensure the password syncs together, which can be located within the advanced tab.

Once you've configured the cross domain security and restarted both weblogic servers, try to import again

About the author

Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.
Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles

Comments

Other Posts

NameID element must be present as part of the Subject in the Response message

ShibbolethSAML

August 7, 2018
Created by: Daniel Redfern
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...

HOW TO provision AD group membership from OpenIDM

OpenIDMICFAD-connector

June 15, 2018
Created by: Daniel Redfern
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

ICFIDMOpenIDMOpenICF

November 8, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

org.forgerock.script.exception.ScriptCompilationException: missing ; before statement

IDMsync.confforgerockopenidm

November 8, 2017
Created by: Daniel Redfern
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statemen

OpenIDMsync.confForgeRock

September 17, 2017
Created by: Daniel Redfern
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...

Caused by: org.forgerock.json.resource.BadRequestException: Target does not support attribute groups

OpenIDMForgeRockICFConnector

September 17, 2017
Created by: Daniel Redfern
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

OpenIDMForgeRockICFConnectorAD

September 17, 2017
Created by: Daniel Redfern
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...

ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_g

OpenIDMIDMGoogleGoogle-AppsICFreconciliation

September 12, 2017
Created by: Daniel Redfern
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...

forgerock-openidm-encryptedjwt-error

OpenIDMIDMForgeRockJWTIAM

August 29, 2017
Created by: Daniel Redfern
Received the JWT error
Read More...

Unexpected character ('¾' (code 190)): expected a valid value

ForgeRock-OpenIDMOpenIDMIDMKeystore

June 25, 2017
Created by: Daniel Redfern
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Read More...