OIM issues: An error occurred while deploying plug-in to OIM

Installer, I would often receive the following popup error, An error occurred while deploying plug-in to OIM.
July 11, 2015
OIM-11GPluginsJDeveloper

You first need to identify the java file that's causing the issues. When you view the logs again, you'll probably notice the line above will the prefix, INFO [SourceCompiler] after fileObjects . From my experience, these are the java files that compiled successfully. The java file which is being the troublemaker is often not on that list. So it's a good starting point if you have multiple scheduled tasks and/or event handlers

The error, DEBUG [SourceCompiler] Compilation failed. Verify the project classpath. is not necessary a classpath issue but in my experience, a compiling issue of the scheduled tasks and/or event handler. The issue lies with the syntax validation discrepancy with Java Developer and OIM.

I will update this blog progressively over time on new plugin errors though below are my findings to date


Issue 1: Declaring and initiating variables

https://technicalconfessions.com/images/postimages/postimages/_403_3_compiling error with not initiating for loops.png

You must ensure that within 'for' loops, you're initiating the variable. Java does not require you to enter this information here though it's often an old habit by developers. You must ensure that if you're using the first information before the semi-colon, that you in fact initiate and not just declare the int variable (example below)

https://technicalconfessions.com/images/postimages/postimages/_403_4_initiating the for loop makes the compiling successful.png

This will not cause a Java Developer syntax error though will in fact throw An error occurred while deploying plug-in to OIM error if you tried to deploy the code.


Issue 2: Enhanced for loops are prohibited

This is an elaboration of the first issue though enhanced for loops are prohibited. Again you can enter in the correct syntax and Java Developer won't say a word, though when it comes to compiling and deploying to OIM, you'll get the error that it could not be deployed along with the 'complication failed' error as above (see error)

https://technicalconfessions.com/images/postimages/postimages/_403_6_enhanced for loops not allows for OIM plugins.png

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

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...

OpenDJ Error - Connect Error Result Code: 91 (Connect Error)

OpenDJLDAPldapsearchForgeRock

June 5, 2017
Created by: Daniel Redfern
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
Read More...