IDM ERROR - JDBC repository configured but datasource default was not found

IDM ERROR - JDBC repository configured but datasource default was not found
May 23, 2017
ForgeRockIDMJDBC

ISSUE

When starting up ForgeRock's openIDM (IDM) environment, I would receive the following error response:
Using boot properties at C:\Production_Runs\openidm\touro\conf\boot\boot.properties org.forgerock.openidm.repo.jdbc.impl.Activator start
SEVERE: JDBC repository configured, but datasource "default" was not found - must specify or configure a valid datasource for JDBC repository to use.


SOLUTION

https://technicalconfessions.com/images/postimages/postimages/_441_2_Initial JDBC error ForgeRock.png

I fairly simple process to resolve though the OpenIDM error occurs because there's another step that was not there before. This error occurs if you're upgrading ForgeRock's version of 3.x to 4+


1. Step 1: Modify the datasource.jdbc-default.json file

https://technicalconfessions.com/images/postimages/postimages/_441_3_default datasource required.png

Firstly, modify the datasource.jdbc-default.json file to ensure that you're pointing to the database. An example of the datasource.jdbc.default.json file can be located within the openidm\db\mssql\conf directory. Ensure that the datasource.jdbc-default.json file is located within your package


2. Replicate repo.jdbc.json file

Copy the repo.jdbc.json file to the conf directory. Also, delete the repo.orientdb.json file if you're intending to use an alternative database. You shouldn't be using orientdb in PROD anyhow. last time I checked, ForgeRock advocated that oridentdb instances should only be used for non-production


3. Copy over JDBC jar file

https://technicalconfessions.com/images/postimages/postimages/_441_5_JDBC sqljdbc for openIDM.png

You must also remember to create the JDBC driver for MSSQL. The ForgeRock document provides a good insight on this OpenIDM requires an MS SQL driver that must be created from two separate JAR files


4. Move the datasource.jdbc-default to the conf

The probable cause to the issue (even though the above is a pre-requisite to integrate ForgeRock IDM with MSSQL) is to ensure that the datasource.jdbc-default.json is located within the package conf directly. This file can be located within the msssql\conf directory within the root path of IDM. This obviously requires modification to comply with your JDBC database connection

Once all 4 steps are complete, perform a restart of openIDM and determine if the issue persists. You should then be able to located the following INFO response when instantiating the OpenIDM service. Within the startup logging, you should be able to see something as follows:

INFO: Registered Crypto SharedKey Service
INFO: Bootstrapping with settings from configuration file C:\openidm\conf\repo.jdbc.json
INFO: Bootstrapping with settings from configuration file C:\openidm\conf\datasource.jdbc-default.json
INFO: Bootstrapping JDBC repository
INFO: JDBC statement batching enabled, maximum batch size 100

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

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...
E_WARNING Error in file posts.php at line 464: fopen(http://www.technicalconfessions.com/images/postimages/postIcons/pp452.png): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

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...
E_WARNING Error in file posts.php at line 464: fopen(http://www.technicalconfessions.com/images/postimages/postIcons/pp444.png): failed to open stream: HTTP request failed! HTTP/1.1 404 Not Found E_WARNING Error in file posts.php at line 464: fclose() expects parameter 1 to be resource, boolean given

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

Tomcat NioEndpoint$SocketProcessor.doRun java.lang.NullPointerException error

TomcatJava-8PKICAS

June 5, 2017
Created by: Daniel Redfern
When initiating the Tomcat instance, the cas-stderr log file will log a SEVERE error logging multiple times every few seconds
Read More...