We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

Rest connector entitlement import

NM
Regular Contributor II
Regular Contributor II

Hi,

We are facing an issue in entitlement import.

Use case - We have two set of entitlement type, for one of them we have an endpoint to fetch the data for other we don't.

for the one we don't have a separate api call we are planning to fetch the details from account import. and will be utilizing cp31 for both (no separate acct entitlement mapping exists for both types).

we have kept one entitlement type as blank and for other added the url in entitlement params. Issue we are facing is it is not importing the entitlement from application endpoint (no calls as checked from logs), If we remove the blank entitlement, it imports the other entitlement type but we get an error at the time of mapping.

 

Entitlement param json below

"entitlementParams": {
"connection": "userAuth",
"processingType": "SequentialAndIterative",
"unsuccessResponses": null,
"doNotChangeIfFailed": true,
"entTypes": {
"Teams": {
"entTypeOrder": 1,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "abc",
"httpHeaders": {
"Authorization": "${access_token}",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "data",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "name~#~char"
},
"disableDeletedEntitlements": true
}
}
},
"Role": {
}
},
"acctEntParams": {
"processingType": "acctToEntMapping"
}
}

3 REPLIES 3

Dhruv_Sharma
Saviynt Employee
Saviynt Employee

Hi @NM 

Thanks for reaching out to Forums regarding the above query. Could you please provide additional details like the error message in logs and complete JSONs. Please hide/exclude sensitive information (if any).

Regards,

Dhruv Sharma

NM
Regular Contributor II
Regular Contributor II

Hi Dhruv,

I don't see any error message in logs..It is not calling "Teams URL", Role entitlement type we are not importing separately just storing it in cp31 for mapping.

JSON

"entitlementParams": {
"connection": "userAuth",
"processingType": "SequentialAndIterative",
"unsuccessResponses": null,
"doNotChangeIfFailed": true,
"entTypes": {
"Teams": {
"entTypeOrder": 1,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "abc",
"httpHeaders": {
"Authorization": "${access_token}",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "data",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "name~#~char"
},
"disableDeletedEntitlements": true
}
}
},
"Role": {
}
},
"acctEntParams": {
"processingType": "acctToEntMapping"
}
}

Dhruv_Sharma
Saviynt Employee
Saviynt Employee

Hi @NM 

Can you please share the complete postman response for the both the call in the text format, with the postman screenshot as well?

Regards,

Dhruv Sharma