I created a new JDBC connector that reaches out to an MS SQL database for create/modify for new userid. I set up the connector via the web console mostly. I was using the VSCode extension for ISC to review all the configuration and noticed that there was no provisioning policy when one was created in the UI. I’m unable to even create a new one from the extension, as I’ll get the same error either by expanding the tree or attempting to add a new policy under this specific connector.
The kicker is that I can view the provisioning policy with REST API.
Is there something I can check that may have been mis-configured that would cause this error?
Here is the error we get:
cannot open idn://.identitynow.com/v3/sources/provisioning-policies/CREATE. Detail: Unable to read file ‘idn://.identitynow.com/v3/sources/provisioning-policies/CREATE’ (Error: Unable to read file ‘idn://.identitynow.com/v3/sources/provisioning-policies/CREATE’ that is actually a directory)
While actively looking at this issue, I noticed when I tried to also explore the Identity Attributes tree in the VScode extension I got this error:
Element with id d0650fe3a27f4cab87f687671f5964ed/searchsam is already registered
I am using searchsam (userid) in both this new and the existing connector that will be decommed.
Hi @moss_snake_01 ,
Unlike other connector the JDBC won’t have the create profile page hence there is no provisioning policy for it .Therefore you are getting error.For provisioning like create ,modify, delete and update operation for jdbc connector you have to create a connector rule for it and patch it to the source. When an account creation is triggered, the connector will create the account based on the attributes defined in the rule, and the same applies for other operations.
Refer the below documentation for JDBC connector -Provisioning.
I observed the same too. This seems to be a bug from UI page of SailPoint. Whenever you create a provisioning policy from the new UI, the required name attribute for the policy is empty. When you query the policy from API, you can observe that the name attribute is not populated.
Here is how you can fix it, update the policy with any relevant name or simply “CREATE” through the API. After that, you would be able to view/edit it via Visual Studio too.