home / ICF

Category: ICF

AD OIM 11gR2Ps2 integration for reconciliation users

  I'm blogging the process on how to integrate OIM 11gR2PS2 with AD by using the connector server.

OIM 11g/AD connector: The value for a key [IT Resource Name] is not defined in the provided map

  When starting work with the OIM/AD connector and following the step by step processes on and updated (yet incomplete) OIM/AD integrated documentation, I noticed I was getting the following error:

OIM 11g/AD connector: The value for a key [Host] is not defined in the provided map

  When starting work with the OIM/AD connector and following the step by step processes on and updated (yet incomplete) OIM/AD integrated documentation, I noticed I was getting the following error:

OIM AD Connector error: InvalidCredentialException: Remote framework key is invalid

  When setting up the identity connector, I would receive the following error when trying to run an ad-hoc schedule task

OIM AD recon Integration: 'Connector ConnectorKey not found'

  When integrating OIM with AD, I was receiving an 'Connector ConnectorKey not found' error when running the schedule task.

OIM AD Connector Error: Unable to get the Directory Entry

  When working on the OIM AD integration, I came across the following error

Access Denied when setting ICF connector key

  When setting up the connector server key, I would receive an 'access denied' with a System.UnauthorizedAccessException trace System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\Identity Connectors\Connector Server\r2dadszy.tmp' is denied.

OIM 11g Connector Server - Access Denied

  The connector server is required to provide the interoperability to provision and to recon' between the target system and your OIM instance.

ConnectorServer.exe Error: 0 : Exception occured starting connector server

  Once reviewed within the connector server logs, I would see the following error: ConnectorServer.exe Error: 0 : Exception occured starting connector server

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

  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

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

  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.

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

  When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error

ForgeRock OpenIDM - InvalidCredentialException: Remote framework key is invalid

  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.

Comments