Keep existing entitlements during import (REST connector)

[ekorh]

Hi,

We would like to implement a following solution. Please provide us information on this:

If user gets imported accesses, when importing accounts accesses to Saviynt, Saviynt should keep the existing entitlements as well.

So, e.g.

User only has access 'abc' in import.

User already has accesses 'abc','xyz' and '123'

All of these (abc, xyz, 123) should be still visible for user in Saviynt after import.

All accesses have to be under same entitlementType.

Best,

Ella

[rushikeshvartak]

Please confirm if below understanding is correct.

Irrespective of import job of account to entitlement. entitlement should not be removed from Saviynt.

if yes please enable recon=false under entitlement Type

[ekorh]

Hi,

Thank you for the proposal. We tested this but still after running the access import job, the entitlement not in the response was deleted from the account.

We disabled recon from the entitlementType, provisioned entitlement a for the account, ran access import (response contains only entitlements b and c for the account), entitlement a is not visible for the account anymore.

[rushikeshvartak]

Can you share logs & accountsImport json

[ekorh]

Hi,

The thing is that if we this working and don't recon the entitlementType wouldn't that still block us from knowing out of band accesses? See, we are using only one entitlementType for all entitlements in this integration. The response where we read the access data is not supporting multiple entitlementTypes configuration.