When initiating the openIDM startup while connected to the orientDB database, I would rarely (though often enough to blog about it). a startup issue with the following error response:
org.forgerock.json.JsonException: org.forgerock.json.crypto.JsonCryptoException: javax.crypto.BadPaddingException: Given final block not properly padded
Unexpected character occurred when the IP addresses changes and the virtual instance was migrated into a separate network subnet.
Received the JWT error
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
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.
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
comments powered by Disqus.