AddAccess - ExistingComments

[Jillustre]

Hi,

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?

thanks

[rushikeshvartak]

• Can you share logs ?
• which connector is used?
• Did you added entitlement with new account  configuration under endpoint?

[Jillustre]

• Here is the log after I re-run the provisionning job
• Connector is REST,  the ADDAccessJson call an inhouse API
• Yes

[Jillustre]

@rushikeshvartak any clue?

[rushikeshvartak]

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

[Jillustre]

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?

[avinashchhetri]

@Jillustre,

The ecm-worker service will have your Provisioning/ Job Run related logs.

[Jillustre]

here is the log emc-worker

[Jillustre]

@avinashchhetri @rushikeshvartak  Anything that tell us what happen?

[rushikeshvartak]

Does entitlement gets added in target ?

Do you see any error in provisioningcomments section of tasks

[Jillustre]

@rushikeshvartak 

No entitlement  added in target

No error in provisioningComments section of the task. only in Existing Comments:"

Entitlement with new account for this application Account Key already exists for the account name. Setting Accountkey in for the Task."

Number of tries for provisioning 5

[rushikeshvartak]

Does other entitlement getting added. does your add access json exist in connection & working ?

[Jillustre]

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

Regards,

[rushikeshvartak]

Please share AddAccessJson or try to hardcode access_token in Json & try

[Jillustre]

The AddAccessJson is not even triggered on provisionning. If ever and got error because of that, we have error log on our API. 

{
"call": [
{
"name": "Role",
"connection": "userAuth",
"url": "https://OurApiUrl",
"httpContentType": "application/x-www-form-urlencoded",
"httpMethod": "POST",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpParams": "{\"employeeNumber\":\"${user.employeeid}\",\"applicationId\":\"${entitlementValue.entitlementID}\",\"createdById\":\"3880\"}",

"successResponses": {
"statusCode": [
200,
201,
202,
203,
204
]
},
"unsuccessResponses": {
"statusCode": [
404,
401,
400
]
}
}
]
}

[Jillustre]

@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.

[rushikeshvartak]

Does entitlement having entitlement id

[Jillustre]

Yes it have... 

[rushikeshvartak]

select entitlementid,entitlement_value from entitlement_values where entitlement_value='157'

Share output

[Jillustre]

It's 151 and not 157, here is the result

[rushikeshvartak]

Please share postman screeshot

[Jillustre]

Hum, not sure what you mean ... I'm not using postman for this

[rushikeshvartak]

Which connector is used for application ? if REST then does same API is working from POSTMAN ?

[sk]

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?

[Jillustre]

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.