JDBC Connector Connection issue: Missing Required Jar

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

I have a JDBC Source that was working, however it stopped connecting. I am getting the following error:

We have detected an error from the managed system.

Error Received:
[ InvalidConfigurationException ] [ Possible suggestions ] Verify that the driver details are correct/Missing required jar. [ Error details ] Error occurred before establishing the connection with Server. java.lang.ClassNotFoundException : test configuration

The issue seems to have started after I tried creating another JDBC source with a jar named ojdbc8.jar. I thought maybe the upload overwrote the original jar since they had the same name and there was only 1 copy on the VA.

I have tried re-uploading the ojdbc8.jar driver from 19.12, 21.22, and a couple in between. None have worked. I also tried renaming the file to a unique name, but those either fice a timeout after 15 seconds, or still do not show up in the VA.

I am checking on the VA with this command:

sudo docker exec ls -al /opt/sailpoint/ccg/lib/custom

I have also tried waiting as other threads suggested. I’ve waited 10 minute after upload, and same after hitting save.

I have tried restarting the CCG after saving, and also tried restarting the whole VA without success.

Is there a way to clear out the existing jar files on the VA and then re-import the jar files? I tried removing the file from the source and saving it, then restarting the VA/letting it sit but neither removed them.

Any help would be great.

2

One thing I am seeing is that there are 2 OJDBC8 files on the VA when I use the command above:

Screenshot 2024-06-01 at 10.46.17 AM
Screenshot 2024-06-01 at 10.46.17 AM775Ă—167 17.2 KB

I am unable to get either of these to be removed. I have verified that the ojdbc8_19C.jar is not used in any connector, and I have removed the ojdbc8.jar from the JDBC Connector I am working with, and it still persists.

The environment has a single VA. There is another VA to another environment, which also has a an Oracle DB, but those should be separate.

So what steps can be taken to get the old jar files removed?
I would like to remove the second one and see if that is part of the issue.

Is there a way to tell that the correct version has been updated? Many topics suggest trying renaming the file, but that does not seem to be getting uploaded.

Is there a way to get better visibility into if and when the jar file is being uploaded to IDN and subsequently when it is downloaded to the VA?

3

Hi @gmilunich – I noticed this morning that all of my client’s JDBC applications’ aggregations failed as of today, also with the same “Missing Required Jar” error (then found your post searching for info). We haven’t made any changes to the .jar files or JDBC app configurations over the past few days, as far as I know, so I wonder if this is some kind of product issue or outage.

4

That could be possible. My issue coincided with the the timing of my setting up the other connector, but they may not have actually been related.

I will have to check the other JDBC connectors and see if they are having issues too or if this is isolated for this.

5

@AlexFKing - When did this start happening for you? Have you been able to get them working again? Ours started on Friday and I have tried Several times over the course of the weekend with no luck.

I am starting to wonder if there is an issue with it getting uoloaded. Today I noticed that when I look at the Source through the API that it shows the uploaded file history right after save is pressed, but still not working for me. I checked on the VA Using teh command above, and I am only seeing the two previous jar files, not the newest one. I am trying it with 19.22 which is the latest version for 19 and confirmed to work with jdk8.

For reference, this is the one I have downloaded:

Screenshot 2024-06-02 at 4.26.59 PM
Screenshot 2024-06-02 at 4.26.59 PM1589Ă—1037 166 KB

I have found the following similar topics, but none of those suggestions have worked so far:

This has the same error I am getting.

  • I have been restarting the VA after upload from the UI. Not working.

I looked at this one, and it seems that the original question never was answered, and it would be useful here if someone does know the answer.

https://community.sailpoint.com/t5/IdentityNow-Forum/IDN-JDBC-Test-Connection-error/m-p/232735
This article suggest that we upload the file directly to the VA, but this should not be required for this. I also don’t have access to do this at the moment.

This ticket has the same error, and the issue was with the Jar file the user was using. This leads me to believe that there is an issue with the Jar not getting set correctly, but none of the solutions appear to resolve this. I tried the steps of changing the VA it was pointed to and then switching back, but that did not help either.

6

Hi Geoff,

We have a JDBC source that we’re still in the process of onboarding.
It has worked just fine in the past, but now it seems that it is failing with the same issue as you have.
It’s been in failed state for 2 weeks apparently.

Though we use mssql-jdbc-12.6.1.jre11.jar instead of ojdbc.
Did you log a support ticket for this already?

I just tried deleting / re-uploading the file and it’s still failing.
Have tried to restart the VA cluster as well.

Will keep you posted if I find anything.

When I initially created the source I also had to wait quite some time for it to work…
We don’t have any other sources that use JDBC so no conflicts

image
image1302Ă—95 6.29 KB

7

We are also seeing the same behaviour in our sandbox environment (fortunately not in Prod).
For us, the issue started since 1st July and failing for all JDBC sources.

Looks like a recent change by SailPoint might have caused this.

8

I’m seeing the same issue as well in our sandbox environment. Has someone been able to confirm if this has been caused by recent sailpoint change?

9

We are having the same issue in the Sandbox also. Sources that have not changed for a long time and has been working correctly until 1/2 days ago

10

SailPoint just confirmed this as an issue on the Status Page https://status.sailpoint.com/

image
image905Ă—213 7.54 KB

1 Like
11

Looks like SailPoint just opened an Incident for this: https://status.sailpoint.com/incidents/892myfn54zj2

Edit: @edmarks beat me to it by 1 minute

1 Like
12

Looks like they have Identified the issue:

1 Like
13

Hi @gmilunich & @edmarks,

It’s still not working for our non-prod JDBC sources. Is there anything we need to do from our end to implement the fix?

14

@maheshtare
What is your current ccg version? I think the fix is with 988 - if your ccg version is lower you will need to initiate update.

15

Hi @oliver_goebel2,

Its 985. I have raised a support ticket to get it updated. But it should have been automatically updated to the latest version right?

16

I know that Support was rolling out the updated version to those customers with support tickets first, but it should be rolled out to all customers by now (unless they are doing a staged rollout.) If you restart the VA, it should check for updates and run them upon restart.

If the restart doesn’t work, then reach out to Support to inquire. It has been over 24 hours so I would expect all VAs would have received an update by now, so something else may be affecting the update of your VA.

17

Adding the details from the Support site for reference:

Screenshot 2024-06-05 at 7.44.02 AM
Screenshot 2024-06-05 at 7.44.02 AM1716Ă—1926 331 KB

18

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.