IDM ERROR - JDBC repository configured but datasource default was not found
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
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
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
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
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