JDBCProvision rule rejected: "Remove reference to PreparedStatement / executeQuery / executeUpdate" (400.1.3 Illegal value)

Hi all,

Since early November 2026, I cannot save or update a JDBC provisioning rule (type JDBCProvision) that runs SQL. The same rules saved fine until about November 4, 2026.

The error from the API (PUT /beta/connector-rules/{id}) and from the VS Code extension is:

HTTP 400, “400.1.3 Illegal value” for field “sourceCode.script”:
[{“line”:2,“column”:17,“message”:“Remove reference to PreparedStatement”}, {“line”:40,“column”:23,“message”:“Remove reference to executeQuery”}, {“line”:74,“column”:8,“message”:“Remove reference to executeUpdate”}, …]

Only these three words are reported on every line where they appear. Other JDBC calls, such as connection.prepareStatement(…), ResultSet and SQLException, are not reported.

A minimal example of the pattern in the rule:

import java.sql.PreparedStatement;
PreparedStatement st = connection.prepareStatement(“UPDATE my_table SET my_col = ? WHERE id = ?”);
st.setString(1, value);
st.setString(2, id);
st.executeUpdate();

This is the same pattern as in the documented JDBC Provision Rule sample, so I did not expect it to be blocked.

I have opened a support case. Meanwhile:

  1. Has anyone else seen this since early November?
  2. Is this an intended restriction? If it is, what is the supported way to run INSERT, UPDATE and DELETE statements from a JDBC provisioning rule?

Thank you.

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

Hello @SivaLankapalli ,

I have just tested it, and I do see the same issue. It was working a week back. Seems this is a bug to me. Recommend checking with support team

Hello Siva. Yes, others have reported this. Theja reproduced it here, and Rainiel, Lucas, Federica, Suhasini and others reported similar failures in this thread. Rainiel also shared that SailPoint Support attributed it to a recent update and was working on a fix.

This looks like a validation regression. SailPoint’s official JDBC Provision Rule example still uses PreparedStatement and executeUpdate() for INSERT, UPDATE and DELETE, and I do not see PreparedStatement, executeUpdate() or executeQuery() in the published Rule Code Restrictions. Since the API also rejects the rule, this is unlikely to be a VS Code issue. I would leave existing deployed rules unchanged and verify provisioning still works.

For new implementations, Vikas’s suggestion is a supported alternative. The VA-based JDBC connector supports SQL queries or stored procedures without a rule. However, it is not a direct replacement for custom logic, and Update Account requires Attribute Sync for the affected attributes.

I have not found a verified workaround within the rule. Since you already have a Support case, I would share these references and ask for the fix and rollout status.