SAV Role should be added to user instead of Sav4Sav account

[SudheerKaneti]

Hi Team,

I want to know the feasibility of adding SAV roles directly to the user. Currently the sav role is adding as an entitlement to the SAV4SAV account after the request is completed in ARS.

We have used SAV4SAV rest connector to get all Sav rules as entitlements so that the sav roles can be visible in ARS.

The requirement is, after the request is completed in ARS for the SAV role, not only the account but also the user should get the sav role. Is there any way we can achieve this?

Thank you,

Sudheer Kaneti

[rushikeshvartak]

Share addaccessjson

Working json 

{
   "call":[
      {
         "name":"SAVRole",
         "connection":"acctAuth",
         "url":"https://dev.saviyntcloud.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
        ]
       }
      }
   ]
}

[SudheerKaneti]

Hi Rushik,

Thank you for your response. The SAV role is adding to the account, but I want the SAV role to be added to the user at the user level as well.

Is there any feasible way to configure it.

Thank you,

Sudheer Kaneti.

[rushikeshvartak]

Above api will add to user level also.

i hope you are using automated provisioning as on

[CR]

@SudheerKaneti 

SAV role every users need add means default role or requested SAV Role?

[SudheerKaneti]

Hi Rushikesh,

I have checked but Sav roles are not assigning to the user level but are assigning to the account level.

I have marked automated provisioning as ON in security system.

Thank you,

Sudheer Kaneti.

[rushikeshvartak]

Share connection JSON

[SudheerKaneti]

Hi Rushikesh,

I do not have connection JSON. It was all prepopulated when I enabled SAV4SAV connection in global configuration.

Thank you,

Sudheer Kaneti

[Sivagami]

Which API your add access json calls? 

-Siva

[SudheerKaneti]

Hi Shivagami,

The add access JSON that I have used is:

{
   "call":[
      {
         "name":"SAVRole",
         "connection":"acctAuth",
         "url":"https://dev.saviyntcloud.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
        ]
       }
      }
   ]
}

Thank you,
Sudheer Kaneti

[SudheerKaneti]

Hi All,

Thank you for all your responses,

We have actually found the issue and issue lies with the incorrect URL's in all JSONs. The platform recently moved from migration testing environment to Dev environment after testing the upgrade v23. Even after moving from migration env to Dev env, the URLs in the JSON is still migration env URL in the SAV4SAV connection and not updated with new dev env URL which causing the issue.

We want to confirm whether we can reconfigure SAV4SAV connection again so that it updates all JSON's with new URLs? Currently the option is grayed out

If not, we will update all the URLs and connection JSON manually.

Thank you,

Sudheer Kaneti.