JDBC Provisioning rule writing null values

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

I have a working JDBC provisioning rule but I have found it is filtering values that already match so writing null values.

We have read-only access to application MSSQL database table so write to an alternate table for provisioning that the application then imports from.
*Some fields don’t allow null values so write operation frequently fails
*We need to send a complete record on any attribute change otherwise the application import job overwrites valid values with null

IdentityNow-Rule-Guide-JDBC-Provision-Rule comments mention turning nofiltering to true but doesn’t provide any documentation.

Google AI returns:

  • By default, SailPoint IdentityNow may not send attribute changes to the connector if the value being sent is identical to the existing value in the link object.
  • noFiltering=true: Setting this flag to true in the provisioning plan instructs SailPoint to bypass this filtering mechanism.

We tried using aliases as mentioned by ‘bilal’ in this article but then we can’t turn on attribute sync for those attributes. There are a lot of articles for IIQ and workflow but not ISC JDBC Provisioning Rules.

I found ProvisioningPlan.GenericRequest for setting an argument but all my attempts at setting ‘nofilterting=true’ have failed.

Same behavior was mentioned in this post but he found a solution that worked without needing to turn off filtering.

This post talks about it for IIQ but not ISC>

Any suggestions would be appreciated.

2

Hi @kwhipple can you change your provisioning rule to: read the appropriate row from the application table, apply the updates from the account request, then write a complete record to the alternate table?