new entitlement is generated instead of overwritten

[Joon]

Hello Team,

I would like to put a description in an AD entitlement by API before we import.

Here's the process I was wishing

1. {{url}}/ECM/{{path}}/createrequest

Create request to generate AD entitlement by calling API.

2. Once the task is completed, we will have the entitlement record in the AD endpoint with GUID and other attributes in ev.Custom properties.

3. By referring to the properties, I call "{{url}}/ECM/{{path}}/createUpdateEntitlement" this API to generate an entitlement in Logical AD endpoint.

4. Entitlement is generated in the logical AD endpoint

5. Running Import Job for the Logical AD to get the AD group which is created #1.

Here's the problem occured.

6. Once the import job is done, the entitlement generated at #4 will be inactivated and new record is created like below.

I would like it to be overwritten from the import job instead of having a new record.

Do you have any idea how to avoid it and get this overwritten ?

[pmahalle]

Hi @Joon ,

Pass Entitlement ID in request payload and try.

"entitlementID":"<provide entitlement id here>"

[Joon]

Hello @pmahalle ,

What I want is to overwrite the Ent created in #3 during #4 .

Currently, It generates a new one like below... and the the one in #3 will be inactivated.

[Joon]

in #1, #3 they will have same entitlement value, so I was expecting to be overwritten. 

[pmahalle]

Hi @Joon ,

What's your reconciliation filed in groupImportMapping in AD connection? Value of that field is same during Entitlement created through API and coming from AD through import?

[Joon]

Hello Paddy,

Reconcilation field is EV.CP13 and Yes, It has same value which is GUID.

The first record was created in #3 and the 2nd record is the one created during the import(#4)

[pmahalle]

Hi @Joon ,

Can you entitlementID for both the entitlements, is it same? Try by adding entitlementid for entitlements you are creating through API.

[Joon]

Hello Paddy,

If I put the entitlementID and run Import, The import job gets failure.. because of duplicate.

Is there any flag that I can use to handle this duplication?

Duplicate entry '4fe109ca-58c3-42c5-8d20-8c7cdead929a-456-CN=RBAC_VAULT_PROD_joon' for key 'ENTITLEMENTID'

[dgandhi]

Try to delete / rename the duplicate entitlement value and then map entitlement id to the original one and do the recon again. It should work.

[Joon]

I have changed Reconcilation_field from CP14 to Entitlement_value like below but the result is same.

During import job, existing ent was inactivated and new one is created.

Can I get some advice ?