10-19-2022 06:30 AM
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?
10-19-2022 06:38 AM
10-19-2022 06:47 AM - edited 10-20-2022 09:37 AM
10-19-2022 10:25 AM
10-19-2022 11:52 AM
since its added as part of endpoint its already assigned to account.
Is it assigned to account in target ? in logs can you share time / taskkey you to look for
10-20-2022 09:09 AM
The new account is created but the AddAccess task don't get competed.
for the log do you need all service name to be included?
10-20-2022 09:11 AM
The ecm-worker service will have your Provisioning/ Job Run related logs.
10-20-2022 09:32 AM
10-21-2022 05:18 AM
10-21-2022 08:46 AM
Does entitlement gets added in target ?
Do you see any error in provisioningcomments section of tasks
10-21-2022 09:12 AM
No entitlement added in target
No error in provisioningComments section of the task. only in Existing Comments:"
10-21-2022 10:17 AM
Does other entitlement getting added. does your add access json exist in connection & working ?
10-21-2022 10:34 AM
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
10-21-2022 10:58 AM
10-21-2022 11:03 AM
The AddAccessJson is not even triggered on provisionning. If ever and got error because of that, we have error log on our API.
12-12-2022 12:43 PM
@rushikeshvartak any update on this? we took a break on it and just tried it again today and same error in existing comments
Entitlement with new account for this application Account Key already exists for the account name. Setting Accountkey in for the Task.
12-12-2022 12:54 PM
12-13-2022 04:16 AM
Yes it have...
12-13-2022 09:10 AM
select entitlementid,entitlement_value from entitlement_values where entitlement_value='157'
12-13-2022 09:14 AM
It's 151 and not 157, here is the result
12-13-2022 10:55 AM
12-13-2022 12:40 PM
Hum, not sure what you mean ... I'm not using postman for this
12-13-2022 12:50 PM
Which connector is used for application ? if REST then does same API is working from POSTMAN ?
12-12-2022 01:53 PM
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?
12-13-2022 04:20 AM
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.