Unrecognized Entitlement & Continuous Provisioning during Identity Refresh Run

Hi, we are facing an issue for our JDBC connector where the provisioning is being triggered during every Identity Refresh. Did anyone face this issue before?

Hi Ang,
Thank you for your post. Could you please let us know if you have any Role created with any membership criteria which satisfies after the refresh and it is triggering any provisioning ?

Can you please share more details on the provisioning process getting triggered? Is it Attribute sync or Add Entitlement?

If Add Entitlement, then provide more info as @RAKGDS mentioned. If attributes syncing, then share your Create Account Prov policy and Attribute sync list

Both can trigger the provisioning, but for JDBC it is the provisioning code which will get executed.

Thanks

Role has been created with membership criteria is met.

Is adding entitlement that associated to the role on every identity refresh.

Do you see the same entitlement under the identity who is being provisioned repeatedly?

It seems to me like the JDBC rule is not set to add the entitlement to the user in Downstream and IDN is trying to add it again and again

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.