Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

REST Connector Remove Access not working

rakesh
New Contributor
New Contributor

Hi Team,

Trying to remove access for a REST based application, from postman access removal is successful,but from Saviynt, i am not getting any response back from the target.

Using graph APIs for connecting to Microsoft Intune (MAM), below is the remove access JSON the we're using:

{
"call": [{
"name": "call1",
"callOrder": 0,
"connection": "userAuth",
"url": "https://graph.microsoft.com/v1.0/users/${account.accountID}/wipeManagedAppRegistrationsByDeviceTag",
"httpParams": "{\"deviceTag\":\"${entitlementValue.customproperty1}\"}",
"httpMethod": "POST",
"httpContentType": "application/json",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json",
"successResponses": {
"statusCode": [204, 200]
},
"unsuccessResponses": {
"statusCode": [403, 404]
}
}
}]
}

API reference Link: https://learn.microsoft.com/en-us/graph/api/intune-mam-user-wipemanagedappregistrationsbydevicetag?v....
Btw in postman getting response code 200 instead of 204 as per Graph API.


Regards,
Rakesh

3 REPLIES 3

Manu269
All-Star
All-Star

JSON seems to be fine.

  • Add {"showLogs":true} against ConfigJSON param in your connection to print additional logs.

 

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

naveenss
All-Star
All-Star

Hi @rakesh ,

In the below JSON, try replacing <entTypeName> with the entitlement type name of the entitlement.

{
  "call": [
    {
      "name": "<entTypeName>",
      "callOrder": 0,
      "connection": "userAuth",
      "url": "https://graph.microsoft.com/v1.0/users/${account.accountID}/wipeManagedAppRegistrationsByDeviceTag",
      "httpParams": "{\"deviceTag\":\"${entitlementValue.customproperty1}\"}",
      "httpMethod": "POST",
      "httpContentType": "application/json",
      "httpHeaders": {
        "Authorization": "${access_token}",
        "Accept": "application/json",
        "successResponses": {
          "statusCode": [
            204,
            200
          ]
        },
        "unsuccessResponses": {
          "statusCode": [
            403,
            404
          ]
        }
      }
    }
  ]
}

 

 

 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

rakesh
New Contributor
New Contributor

Thanks Naveen. Your suggestion worked!!!