How are we calling stored procedures for provisioning operations in JDBC connector

[AsGoyal (Aayush Goyal)]

Hi All,

How are you guys calling a stored procedure to do provisioning operations like create/update account in a jdbc source under provisioning queries.

Are you facing issues with the same?

[suraj_gorle]

Hi @AsGoyal ,

You can call a stored procedure in the JDBC connector under Provisioning Queries, as shown below.

Although I have previously used SQL queries and they worked fine, I did not get a chance to test a stored procedure after this update. Are you currently facing any errors while executing it?

Thank you.

[AsGoyal (Aayush Goyal)]

Hey @suraj_gorle ,

I tried this and I am getting error executing this query.

[suraj_gorle]

@AsGoyal

I tried this and I am getting error executing this query.

Can you please share the error also value is populating as per expectation in plan ?

[Deepak_Chaudhary]

@AsGoyal

How are you guys calling a stored procedure to do provisioning operations like create/update account in a jdbc source under provisioning queries.

HI @AsGoyal SailPoint’s JDBC connector supports executing stored procedures by using callable statements in Provisioning Query blocks.

Could be please let us know what operation you are trying to achieve for eg. create,update,disable accounts using procedures ?

[AsGoyal (Aayush Goyal)]

Hi @suraj_gorle @Deepak_Chaudhary ,

Error I am getting.

Caught exception: attribute is not added as part of provisioning plan:entitlement_name

[suraj_gorle]

@AsGoyal

entitlement_name

Hi @AsGoyal ,

Have you checked in account activity whether above attribute is passing or not ?

[AsGoyal (Aayush Goyal)]

Hi @suraj_gorle ,

I see all the attributes under attribute requests correctly.

[Deepak_Chaudhary]

Hi @AsGoyal

As the error mentioned by you so you need to check the provisioning plan and verify the attribute might not defined in your JDBC source and add the same then run the query.

First thing - you can check entitlement_name is added to your Create Profile or Update Profile. All the defined attributes must exist in the policy to be passed in the plan.

Second thing - As entitlements are often handled as separate AttributeRequest objects within the AccountRequest. In this case if trying to fetch the entitlement value then it will give null.

Third thing - Try to use getAttributeRequestValue Utility instead of calling .getValue() directly on a null object.

AttributeRequest atReq = accountRequest.getAttributeRequest(“entitlement_name”);
if (atReq != null)

{
String value = atReq.getValue();

}

Go through the discussions on the same if works for you:

Why does attributes set in JDBC modify account provisioning policy not come up in provisioining plan in IDN

Hi Team, I was working on onboarding a new JDBC source in my tenant. As part of this I have attached a modify account provisioning policy to the source with “usageType”: “UPDATE”, but I not see the attributes added in the provisioning policy coming in the provisioning plan when there is modify account request. I had found a work around and I just queried the target database itself to get the required user attributes in my provisioning plan, but this has a technical downside and I cannot use thi…

How to fetch the entitlement attributes in JDBC Provisioning Rule

Hi Everyone, How to fetch the entitlement attributes in JDBC Provisioning Rule. Apart from the entitlement ID and entitlement Name from the below image. Below is the attachment for the reference. [image] Any suggestions would be helpful. Kind Regards, Sai Krishna L

please try all these possible scenarios and let me know if this works for you.