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

httpAccToEnt - {id} substitution error

Paul_Meyer
Regular Contributor
Regular Contributor

I have an entitlement endpoint that returns the list of entitlementIDs for a particular user. The http parameters for the endpoint is: /SecurityUserRoles?$count=true&$filter=UserId eq '<<acccount name>>'

In the ImportAccountEntJSON -> accEntParams -> entTypes -> Roles -> http -> url setting, the url has the following value:

"url": "https://hostname/Data/SecurityUserRoleOrganizations?%24count=true&%24filter=UserId%20eq%20%27${id}%2...",

When executing the Access full recon job, from the debug log, it seems the endpoint is called for each application account, however for each Webservice url, the following error is encountered:

Calling Webservice Url - https://hostname/Data/SecurityUserRoleOrganizations?%24count=true&%24filter=UserId%20eq%20%27${id}%27 with httpParams - null

DEBUG rest.RestProvisioningService - Got Webservice API Response: [error:Error Illegal character in query at index 128: https://hostname/Data/SecurityUserRoleOrganizations?%24count=true&%24filter=UserId%20eq%20%27${id}%2...

Where index 128 is at the start of the dollar sign in the url "${id}".

From past experience such an error means if the variable substitution string "${id}" shows up in the actual web service call url, that the variable is not in the substitution variable name space or the incorrect substitution variable name is used.

From the v5.5, and other versions, Rest connector Developer's Handbook, the httpAccToEnt section states that "${id}" must be used. Also looking at other forum posts, it seems only "${id}" is 'allowed'.

Is there another substitution variable that needs to be used or is the url setting configured incorrectly fro the required http parameters the endpoint requires?

 

1 REPLY 1

rushikeshvartak
All-Star
All-Star

can you share postman screenshot


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.