Saviynt unveils its cutting-edge Intelligence Suite products to revolutionize Identity Security!
Click HERE to see how Saviynt Intelligence is transforming the industry.
Saviynt Copilot Icon

Custom REST API Connection

aidanryan
New Contributor III
New Contributor III
We are trying to do a custom connection to InEight using a REST connection. Currently, we are stuck on the CreateAccountJSON. We can get it to create the account on Saviynt's side if we removed the userAUTH from the "call1" connection portion of the JSON, but it doesn't provision on InEight's side. However, if we add userAUTH, we get the errors shown in the screen shot's provided. We also tried hard coding the token into the CreateAccountJSON, but still received the same errors.
 
We are able to verify the connection via PostMan, and we are able to get the ConnectionJSON to work because we were able to use the ImportAccountJSON to pull accounts from InEight into Saviynt. We also verified with InEight integrations person that the tokens we are using are indeed valid and so are our httpHeaders. 
 
CreateAccountJSON:

{
    "accountIdPath": "call1.message.id",
    "dateFormat": "yyyy-MM-dd'T'HH:mm:ssXXX",
    "responseColsToPropsMap": {
        "accountID": "call1.message.employeeid~#~char"
    },
    "call": [
        {
            "name": "call1",
            "connection": "keep-alive",
            "url": "https://.com/integrations/v1/Users/Import",
            "httpMethod": "POST",
            "httpContentType": "application/json",
            "httpParams": "{\"FirstName\":\"${user.firstname}\",\"LastName\":\"${user.lastname}\",\"EmailAddress\":\"${user.emailaddress}\",\"IsActive\":\"true\",\"DisplayUserId\":\"${user.employeeid}\",\"EmployeeId\":\"${user.employeeid}\",\"SourceSystemId\":\"${user.employeeid}\",\"Language\":\"EN\" }",
            "httpHeaders": {
                "": "",
                "": "",
                "Authorization": ""
            },
            "successResponses": {
                "statusCode": "202"
            }
        }
    ]
}
1 REPLY 1

SB
Saviynt Employee
Saviynt Employee

Can you update ConfigJSON param in the REST connection with value {"showLogs":true}; this will print additional logs and may help to identify the issue. Run the prov job and then check for the below strings in the log.

Calling Webservice Url - this will display the Call url with the body being sent from Saviynt.

Got Webservice API Response - this will display the response we get from target.


Regards,
Sahil