When setting up the identity connector, I would receive the following error when trying to run an ad-hoc schedule task
IAM-1020021 Unable to execute job : Active Directory User Trusted Recon with Job History Id:2678 org.identityconnectors.framework.common.exceptions.InvalidCredentialException: Remote framework key is invalid
First of all, you better like my FB page because of this information I am distributing. If you're reading this then you're experiencing the same issue. The only difference between you and I is that the resolution is 1 page length and not a weekend ;-)) There's a number of issues here in setting up the connector on the AD side
Task 1: Ensure you have your AD connector installed on the OIM server AS WELL as the connector (AD) server.
I'm talking about the AD connector server deployed on the OIM side and then the connector server connector deployed on the AD server (or if you're using a designated connector server) then copying over the AD connector server you used on the OIM server into the newly-created connector server.
Ensure that you've installed the connector by following the Install the AD connector with the Connector Server step, which is simply running the wizard.
Then, go to the newly-created directory, which can be located within your program files x86 directory. You need to then download the AD connector (the same on you used within the Install the Active Director Connection Server step)
Once you've down that, extract out the contents of the zip file and place all of those files into the program files x86 directory.
Task 2: Re-run the connector server service
You need complete task 1 before task 2 otherwise the service will not pick up the AD connector that you copied over. This means that you cannot install the service prior to copying over the AD connector.
I would recommend deleting the connector server and then re-installing this. Go into CMD as an administrator (right click and 'run as administrator) and run the following command:
sc delete “Connector Server”
Note:This is the assumption that connector server is called 'connector server'. You can check this by going into servies and looking for the service.
Once you've done that, you then need to run the ConnectorServer.exe command. The example within the CMD shows that there's a /setKey parameter along with a password value Once that's done, you will see a ConnectorServer.exe.config file that get's created.
Then go back into the services window and restart the .Net and Connection Server services
Task 3: Purge the cache
Clearing the OIM cache can be completed by navigating to the $OIM_Server/server/bin directory and running the /PurgeCache.sh All
command. (The 'All' parameter passed will clear all the system properties)
Note:I did however notice that the changes didn't take affect until I restarted both VMs so it may be worth, if available, to restart both servers
Task 4: Password check
Within the IT resource configurations within OIM, you need to enter the clear-text password that you used in the ConnectorServer command. You should not be using the encrypted password located within the ConnectorServer.exe.config file
Once you've checked all of the above, re-run the scheduled task and see if you get a success. Hope this helps!
About the authorDaniel 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
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
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.
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
Received the JWT error
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
When trying to connect, I would then receive the following error "Connect Error Result Code: 91 (Connect Error)"
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
IDM ERROR - JDBC repository configured but datasource default was not found
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded