home / Connector

Category: Connector

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

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

HOW TO provision AD group membership from OpenIDM

  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.

Comments