JDBC-Provisioning Query Settings - Create Account is failing/troubleshooting issue

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

Hello Sailors ,

Im currently working on OOTB feature on ISC for JDBC provisioning operations

Under Query Settiings> Provisioning Query Settings>Configure Provisioning Operations in the Connector – I have enabled this for create
Provisioning Query Settings - Create Account
and the query that i have used somewhat similar to this generic query
insert into databasename.tablename (column1, column2) values ($plan.attribute1$, $plan.attribute2$)
but it is throwing some generic error can someone help me troubleshooting the issue

image
image606×507 18.6 KB

thanks
avi.

2

Hi @amulpuru,

Could you please share the exact error message you’re encountering ?

3

Hi @UjjwalJain ,

i have already shared the error message screenshot and sharing the error message from search page

image
image639×170 11 KB

I dont have access to VA as of now to share detailed logs

thanks
avi

4

Can you verify if all the attributes are correctly mapped and visible in the provisioning plan? You can check this under account request section in search.

5

Hi @UjjwalJain ,

except for autoid and pws

rest all the attributequests were populated from provisioningform

autoid - is a auto generated seq id in target table
psw - is static value

Insert query - insert into demo (autoid, Role, uid, pwd, email)values ((select coalesce(max(autoid),0)+1 from demo), ?, ?,‘xxxx’, ?)

6

Can you check the logs to see if there is a more detailed error message?

Can you run the same query directly against the database and have it work?

In the query, do you mean to have “pwd” or “psw”? All previous mentions have been “psw”, but the query you posted has “pwd”. If this is incorrect in the query, this could be the cause of the issue.

7

Hi @gmilunich ,

My bad while doing data clean up i have misspelled psw as pwd it is nothing to with actual data

1 Like
8

Hi @amulpuru

Since you mentioned that the autoid column is auto-generated by the database, there’s no need to explicitly insert a value into it. Could you try using the following query instead?

INSERT INTO demo (Role, uid, pwd, email) VALUES (?, ?, ?, ?)

Also, have you tested your query directly on the target system to confirm it works as expected ?