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

Use Case / Problem Statement

Add access JSON for REST Connector is not working as expected causing the requested access failing to be provisioned at the target system.
 

Pre-requisites

  • Connection should be successful to the target application.
  • The JSON format should be valid. It can be validated in JSON validator (external tool) for e.g. JSON Validator
  • Add {"showLogs":true} against ConfigJSON param in your connection to print additional logs.
 

Applicable Version(s)

All


Solution

For Add access, in the call name of JSON we have to define the Entitlement Type value. In order to find this, navigate to your Endpoint>Entitlement Type> Click on View detail icon and use the values mentioned under Entitlement Name field. 
sahil_0-1678989351705.png

 


 

Comments
rushikeshvartak
All-Star
All-Star

Entitlement type Name or display name

SB
Saviynt Employee
Saviynt Employee

@rushikeshvartak It is Entitlement Name. 

anuragtripathi
New Contributor
New Contributor

If entitlement type has space in between and we have to make 2 calls for that entitlement type. So how to map responsefromfirst call to second.

Entitlement type: "Group Unit"

mapping response: 

1. response.GroupUnit1.message.locationIds--- this is not working.

2. response.Group Unit1.message.locationIds--- this is not working

 

anuragtripathi
New Contributor
New Contributor

@SB or @rushikeshvartak , Please provide the solution.

Version history
Last update:
‎03/16/2023 01:30 PM
Updated by:
Contributors