SAV 4 SAV provisioning error

[SudheerKaneti]

Hi Team,

I have requested a SAV role through ARS in Saviynt using SAV4SAV connector. The tasks were generated but when I run WS retry job, I am getting error like below.

{"auditDetails":{"call1":[{"headers":null,"statusCode":404,"description":null,"status":"Failed"},{"headers":null,"statusCode":404,"description":null,"status":"Failed"}]},"call1":{"headers":null,"statusCode":404,"description":null,"status":"Failed"}}

SAV 4 SAV connection is successful.

Below is the add access json that I have used.

{

   "call":[

      {

         "name":"SAVRole",

         "connection":"acctAuth",

         "url":https://dev.****.com/ECM/api/v5/addremoveuserfromrole,

         "httpMethod":"POST",

         "httpContentType":"application/json",

         "httpParams":"{\"username\":\"${arsTasks.accountKey.name}\",\"rolename\":\"${entitlementValue.entitlement_value}\",\"operation\":\"1\"}",

         "httpHeaders":{

            "Authorization": "${access_token}"

         },

         "successResponses": {

        "statusCode": [

          200,

          201

        ]

       }

      }

   ]

}

Could you please help me to identify the issue.

Thank you,

Sudheer Kaneti.

[DixshantValecha]

Hi @SudheerKaneti,

We are checking on your request and we will keep you posted.

[DixshantValecha · Accepted solution]

Hi @SudheerKaneti,

The error message you're seeing, "statusCode":404`, typically indicates that the server couldn't find the requested resource. This usually means that the endpoint URL is incorrect or the resource itself does not exist.

Here are a few things you could check:

1. **Endpoint URL**: Make sure that the URL `https://dev.****.com/ECM/api/v5/addremoveuserfromrole` is correct. You might want to try accessing it directly in a web browser or using a tool like Postman to see if it's valid.

2. **Headers and Parameters**: Check if the headers and parameters in your request are correct. The server might be unable to find the resource because a necessary header or parameter is missing or incorrect.

3. **Resource Existence**: The resource (in this case, the role you're trying to access) might not exist. You could check in your application if the role exists.

Remember to replace any placeholders (like `${arsTasks.accountKey.name}`) with actual values before making the request. 

Please Validate the above points and let us know if further assistance is required.

[SudheerKaneti]

Hi Dixhant,

Thank you for the response,

We have actually found the issue and issue lies with the incorrect URL. The platform recently moved from migration testing environment tenant to Dev environment after testing the upgrade v23 but after moving, URLs in the JSON haven't changed in the connection which caused the issue.

Thank you,

Sudheer Kaneti.