We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

AddAccess - ExistingComments

Jillustre
New Contributor III
New Contributor III

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

25 REPLIES 25

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

Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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

Jillustre
New Contributor III
New Contributor III

@rushikeshvartak any clue?

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


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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?

@Jillustre,

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

 

 

Regards,
Avinash Chhetri

Jillustre
New Contributor III
New Contributor III

here is the log emc-worker

Jillustre
New Contributor III
New Contributor III

@avinashchhetri @rushikeshvartak  Anything that tell us what happen?

Does entitlement gets added in target ?

Do you see any error in provisioningcomments section of tasks


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

@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

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


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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,

 

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


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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
New Contributor III
New Contributor III

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

Does entitlement having entitlement id


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Yes it have... 

Jillustre_0-1670933805616.png

 

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

Share output


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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

Jillustre_0-1670951645487.png

 

Please share postman screeshot


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

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

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


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

@rushikeshvartak here is the proof that is working in postman.

Jillustre_0-1680271914824.png

 

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?


Regards,
Saathvik
If this reply answered your question, please Accept As Solution and give Kudos to help others facing similar issue.

Jillustre
New Contributor III
New Contributor III

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.