Issue: User already assigned to groups from backend, but while provisioning Saviynt get 409 error code from API saying - "Role already assigned to user" but it doesn't mark task to complete state. Ideally it should be No action required.
Logs: Got Webservice API Response: [headers:[cache-control: no-cache, no-store, max-age=0, must-revalidate, content-language: en-US, content-length: 149, content-security-policy: script-src-elem 'self', content-type: application/octet-stream;charset=UTF-8, date: Mon, 09 Sep 2024 11:21:48 GMT, expires: 0, pragma: no-cache, server: nginx, x-content-type-options: nosniff, x-correlationid: 10c2009a-2ff5-4a9e-4fe2-cb414ff1c3a1, x-frame-options: DENY, x-vcap-request-id: 10c2009a-2ff5-4a9e-4fe2-cb414ff1c3a1, x-xss-protection: 1; mode=block, strict-transport-security: max-age=31536000; includeSubDomains; preload;], responseText:{error_description":"Role collection already assigned to user",error:"member_already_exists",message:"Role collection already assigned to user"}, cookies:[], statusCode:409]"
Workaround: Modified add access json success response to handle 409 error code and mark it as completed but still same error:
ADD ACCESS JSON:
{
"call": [
{
"name": "groups",
"connection": "acctAuth",
"url": "https://api.removed.hana.ondemand.com/Groups/${entitlementValue.entitlement_value.replace (' ','%20')}/members",
"httpMethod": "POST",
"httpParams": "{\"origin\": \"xxxxx\",\"type\": \"USER\",\"value\": \"${account.accountID}\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
201,
200,
202,
409
]
},
"unsuccessResponses": {
"statusCode": [
401,
400,
404,
405
]
}
}
]
}
Can anyone confirm what should be expected behavior in this case??
My understanding is - if we had 409 in success response code then Saviynt should treat that as success and mark task completed.
Appreciate if anyone can provide their inputs to resolve this.
[This message has been edited by moderator to disable url hyperlink]
