Cannot save JDBC Provisioning Rule with "import java.sql.PreparedStatement"

Hi,

We are currently building JDBC Provisioning rule. Last friday, we were able to create and save the rule. However, when we tried to modify it, it’s getting an error. The error is pointing to line where the “import java.sql.PreparedStatement” is located.

So we tried to remove all the new lines in the code and revert it to the original and tried to save it again. However, the error still appearing and pointing to “import java.sql.PreparedStatement”.

Is anyone experiencing this behavior? even with our existing working JDBC Provisioning Rule, we tried saving it in visual studio even though no changes, it still showing same error.

Hello Rainiel. Since even your unchanged, previously working JDBC rules now fail to save, I would first isolate whether this is a validation or a save issue. import java.sql.PreparedStatement; is valid and appears in SailPoint’s own JDBC Provision rule example, so I would not remove it just because the error points to that line.

  1. Capture the full error from the extension’s Output panel in VS Code, including the HTTP status and any tracking ID.
  2. Retrieve the deployed rule with GET /connector-rules/v1/{id}, then validate its stored sourceCode (version and script) through POST /connector-rules/v1/validate with an ORG_ADMIN token, and check the returned state (OK or ERROR) and details. This tests the exact stored script, not the editor copy.
  3. If validation returns OK but saving still fails, inspect the save/update API response to tell an extension issue from a platform-side failure, since a clean validation does not guarantee the update itself succeeds. If validation returns ERROR on a rule you did not change, review the details and raise a SailPoint Support case.

If the problem isolates to the community VS Code extension, it is not supported by SailPoint, so I would report it to the maintainer there.

Could you share the exact error and your VS Code extension version?

Hi @RAIN

I would recommend following the steps below:

1. Validate the rule using SailPoint REST API

Instead of saving the rule directly through VS Code, validate it using SailPoint’s Connector Rule Validation API.

POST /beta/connector-rules/validate

Submit the complete rule JSON, including the sourceCode.script field.

This helps determine whether the error originates from SailPoint’s backend validation or the VS Code extension.

Can you share the complete error message or the complete rule?

Same here.
With Rules that was already uploaded, now we can’t even edit.

It is blocking HttpURLConnection and PreparedStatement classes, and—much like Lucas—it doesn’t even allow for updating rules that have already been committed.

Provide the rule snap

Hello,

I have the same problem with my JDBC Provision Rule.
I already had a working connector rule on the tenant and only wanted to make some changes, but I am now getting the following errors:

even for me also same issue with JDBC rule . Even i tried using API .. still same error

Hi Rainiel,

Could you try a quick test in a non-production tenant? Create a separate JDBCProvision rule with only this code and try saving it without attaching it to a source:

import java.sql.PreparedStatement;

import sailpoint.object.ProvisioningResult;

return new ProvisioningResult();

Then try saving the same test rule again after removing only the PreparedStatement import.

If both versions save, you could add sections of the original rule back until the error returns. If only the version with the import fails, you’ll have a small example to share with SailPoint Support. If both fail, the issue may not be specific to that import.

Also, if the error includes inline evaluation of, the import may just be showing the beginning of the script. The actual error or line number could appear later in the message.

Yeah, we had a rule that was already deployed and working, but we had to change a few things in the code and this error popped up!

It was working on Friday, and on Monday SailPoint stopped accepting it. Since we’re on a tight schedule, we’re building a whole new connector!

I suggest opening a ticket with SailPoint. As far as I know, this change was made on SailPoint’s side a few days ago, without any warning!

Hello all,

I am also seeing similar behavior. Has anyone found a solution or workaround?

Thank you

Hello everyone,

I’m in the same situation here, i can’t even save a rule that’s already in the tenant with preparedStatement. Also tried changing by api and it doesn’t work.

What is the main reason for using a JDBC rule in your use case when the connector configuration already provides a Provisioning Query option in the UI

I have raised a support ticket with SailPoint regarding this issue. They confirmed that a recent update on their end has caused the issue and that their team is already working on a resolution.

Hi @RAIN,

Just following up to check if there are any updates from SailPoint team on this.

Can you create a new rule and replace it ?

FYI,

It looks like the issue has been resolved, and we are now able to save the rule successfully.