Click HERE to see how Saviynt Intelligence is transforming the industry. |
05/07/2024 01:29 AM
Hi Team ,
, In postman we have only value as input for DELETE . Hence in params I have added value as input but we receive error in log as expecting colon to separate filed name and value. Can you please help on the below JSON.
JSON
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": xxx,
"httpParams": "{\"${account.accountID}\"}",
"httpHeaders": {
"Cookie": "${access_token}",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "DELETE",
"successResponses": {
"statusCode": [
200, 201, 204
]
},
"unsuccessResponses": {
"statusCode": [
400, 403, 401, 404, 409, 500, 501
]
}
}
]
}
05/07/2024 07:56 PM
change httpMethod to DELETEWITHBODY
05/22/2024 05:18 AM
@rushikeshvartak I tried with Delete with body also . it is showing error.
{
"call":[
{
"name":"call1",
"connection":"acctAuth",
"url":"https:/xxx/DeleteUser",
"httpParams":"${account.accountID}",
"httpHeaders":{
"Cookie":"${access_token}",
"Content-Type":"application/json"
},
"httpContentType":"application/json",
"httpMethod":"DELETEWITHBODY",
"successResponses":{
"statusCode":[
200,
201,
204
]
},
"unsuccessResponses":{
"statusCode":[
400,
403,
401,
404,
409,
500,
501
]
}
}
]
}
05/22/2024 09:10 PM
Please share postman curl command [Refer https://codingnconcepts.com/postman/how-to-generate-curl-command-from-postman/ ]
⚠️‼️‼️Do not upload any attachments that contain sensitive information, such as IP Addresses, URLs, Company/Employee Names, Email Addresses, etc.‼️‼️⚠️
05/23/2024 02:20 AM
@rushikeshvartak CUrl command
curl -b cookie.txt -H "content-type: application/json" -H "Accept: application/json" -X DELETE -d "10"
05/23/2024 07:41 AM - edited 05/23/2024 07:43 AM
I have tried even in below way. Still getting error. I have attached logs
{
"name":"call1",
"connection":"acctAuth",
"url":"https://xxx/DeleteUser/${account.accountID}",
"httpHeaders":{
"Cookie":"${access_token}",
"Content-Type":"application/json"
},
"httpContentType":"application/json",
"httpMethod":"DELETE",
"successResponses":{
"statusCode":[
200,
201,
204
]
},
"unsuccessResponses":{
"statusCode":[
400,
403,
401,
404,
409,
500,
501
]
}
}
05/23/2024 09:19 PM
Please share logs
‼️‼️⚠️Keep company-specific private information masked on public forums, such as the name and URL.⚠️‼️‼️
05/24/2024 06:44 AM
05/24/2024 06:55 AM
Does other task are getting completed such as Add/Remove Access?
Error in logs
"2024-05-22T10:36:55.114+00:00","ecm-worker","rest.RestProvisioningService","quartzScheduler_Worker-7-2sh5m","DEBUG","connection: acctAuth"
"2024-05-22T10:36:55.146+00:00","ecm-worker","rest.RestProvisioningService","quartzScheduler_Worker-7-2sh5m","ERROR","Error in processWebservicecom.fasterxml.jackson.databind.JsonMappingException: Can not deserialize instance of java.util.LinkedHashMap out of VALUE_NUMBER_INT token| at [Source: 24634; line: 1, column: 1]"
05/24/2024 07:07 AM
@rushikeshvartak Yeah the log which you posted only we are getting for remove account json. Add access is working fine because we have key and value pair. Remove Access we dont have.
05/24/2024 06:57 AM
05/24/2024 11:22 AM
It looks like the log data is not complete. Can you use the very 1st JSON you added in this forum post and then run the provisioning. You can refer the below link to analyze the api call data and response in the logs.
https://docs.saviyntcloud.com/bundle/REST-v24x/page/Content/Frequently-Asked-Questions.htm
05/27/2024 04:42 AM - edited 05/27/2024 06:39 AM
@SB I have attached logs for below jSON
{
"call":[
{
"name":"call1",
"connection":"acctAuth",
"url":"https://xxx/DeleteUser",
"httpParams":"{\"${account.accountID}\"}",
"httpHeaders":{
"Cookie":"${access_token}",
"Content-Type":"application/json"
},
"httpContentType":"application/json",
"httpMethod":"DELETE",
"successResponses":{
"statusCode":[
200,
201,
204
]
},
"unsuccessResponses":{
"statusCode":[
400,
403,
401,
404,
409,
500,
501
]
}
},
{
"name":"call2",
"connection":"acctAuth",
"url":"https://xxx/Logout",
"httpMethod":"GET",
"httpHeaders":{
"Cookie":"${access_token}",
"Content-Type":"application/json"
},
"httpContentType":"application/json",
"successResponses":{
"statusCode":[
200,
201
]
}
}
]
}
05/27/2024 09:41 AM
The logs still don't look right. Can you try with this JSON and run the provisioning job.
In the logs we need to search for the below highlighted text to ensure we have the right set.
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.
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://xxx/DeleteUser",
"httpParams": "{\"${account.accountID}\"}",
"httpHeaders": {
"Cookie": "${access_token}",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "DELETE",
"successResponses": {
"statusCode": [
200,
201,
204
]
},
"unsuccessResponses": {
"statusCode": [
400,
403,
401,
404,
409,
500,
501
]
}
}
]
}
05/28/2024 08:34 AM
@SB I am not able to get that in logs for remove account , can we connect call and check . It will be better.
05/28/2024 09:05 AM
Does showlogs = true is enabled ?
05/28/2024 09:14 AM
Yes it is enabled, for create account I can see logs as "
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."
For Remove account I am not getting.
05/28/2024 10:37 AM
Can you share whatever logs you are getting.