I've made some test with a request. All approval done, when it came to pending task the NewAccount task completed by provisionning. but for AddAccess, the provisionning run but does not complete. No error on provisionning, but on existing comments, it said -> "Entitlement with new account for this application Account Key already exists for the account name. Setting Accountkey in for the Task."
Is it because of that it dosent go foward to completion? What need to be done to fix this?
No entitlement added in target
No error in provisioningComments section of the task. only in Existing Comments:"
If I complete the task manually, the entitlement get added. But it not trigger the AddAccessJson.
If I tried the AddAccessJson in postman, it work. This is first time we tried the option "Entitlement with Account" All other process with entitlement is working
The AddAccessJson is not even triggered on provisionning. If ever and got error because of that, we have error log on our API.
As part of New Account request are you requesting any other entitlements that are not listed under "Entitlement with Account" ? If so provisioning of those entitlements is working fine?
Yes. We are requesting a role entitlement and it work fine. So our GAP Endpoint have entitlement Employee, on provisionning it give the entitlement to the account of the user. For the entitlement with new account, we have an addAccess task for the other Endpoint named, application tile. but alway receive the comment -> Entitlement with new account for this application Account Key already exists for the account name. Setting Accountkey in for the Task.