When modifying an object within Oracle Identity Manager 11g, in this case, I was modifying/deleting an user, I would be getting the following error:
When modifying an object within Oracle Identity Manager 11g, in this case, I was modifying/deleting an user, I would be getting the following error:
When modifying an object within Oracle Identity Manager 11g, in this case, I was modifying/deleting an user, I would be getting the following error:
IAM-2050243 : Orchestration process with id 389, failed with error message IAM-3010062 : Disabling failed because user TEST.USER1@ORACLE.COM is not synchronized to the LDAP directory..
It was throwing a wobble by stating that the LDAP repository could not be synchronized with the LDAP repository. I was thinking to myself, "what LDAP repository"? In the past, OIM would only allow the LDAP synchronization to be enable during the installation of Oracle Identity Manager. Within OIM 11.1.1.1.5+, the LDAP Sync could be configured manually as part of a post-installation procedure. This includes Oracle Identity Manager 11g Release 2 (11.1.2) and I also imagine OIM 11g PS3 (when it becomes available!)
SOLUTION
Assuming you are not needing the LDAP synchronization, you can disable this by altering the EventHandlers.xml This file can be located within the /db/ldapMetadata directory, which will reside within your OIM_Server/metadata directory
You'll need to import this back into the MDS repository, though if you cannot see the file, you can extract this from the MDS repository, to make the alteration and the then import it back into the MDS. This can be done by following the post, HOW TO: Manually import the metadata for OIM 11g custom plugins
My full path was as follows:
/home/oracle/Oracle/Middleware/Oracle_IDM1/server/metadata/db/ldapMetadata/EventHandlers.xml
You then need to ensure the sync = False for the specific event handlers. It's also worth running the Plugin registering utility or to restart the server application servers. It's also probably worth disabling your scheduled jobs that relates to your LDAP Synchronization.
Once the MDS is re-imported, you should now remove the LDAP sync
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
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
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...
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
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
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...
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...
Tags
Recent Posts
Monthly Activity
Group by date