Click HERE to see how Saviynt Intelligence is transforming the industry. |
08/20/2024 11:09 AM
Hello Team,
We are having issues while disabling account or removing account from Saviynt with the below errors
We are using the below Josn:
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=${URLEncoder.encode(account.accountID, \"UTF-8\")}",
"httpMethod": "POST",
"httpHeaders": {
"X-Api-key": "2****8*****F",
"Accept": "application/json"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
201,
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
401,
400,
403,
404,
405,
409,
502
]
}
}
]
}
Other Url tried:
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=${a...}"
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=<hardcoded accountName/accountID>"
Error:
Got Webservice API Response: [headers:[Cache-Control: private, Content-Type: application/json; charset=utf-8, Server: Microsoft-IIS/10.0, jsonerror: true, X-AspNet-Version: 4.0.30319, X-Powered-By: ASP.NET, Date: Tue, 20 Aug 2024 17:21:23 GMT, Content-Length: 91], responseText:{"Message":"There was an error processing the request.","StackTrace":"","ExceptionType":""}, cookies:[], statusCode:500]
Task Provisioning Comments:
It is working fine from postman:
Full logs:
Solved! Go to Solution.
08/20/2024 11:17 AM
Is this working with hardcoded values ?
08/20/2024 11:23 AM
@rushikeshvartak
It is not working with hardcoded values as well from Saviynt.
Best regards,
GPS
08/20/2024 11:25 AM - edited 08/20/2024 11:27 AM
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"showResponse": true,
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=${URLEncoder.encode(account.accountID, \"UTF-8\")}",
"httpMethod": "GET",
"httpHeaders": {
"Authorization": "${access_token}",
"X-Api-key": "2****8*****F",
"Accept": "application/json"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
201,
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
401,
400,
403,
404,
405,
409,
502
]
}
}
]
}
08/20/2024 11:33 AM - edited 08/20/2024 11:34 AM
Hello @rushikeshvartak
We don't have any connection Json to get the token for this API.
{
"authentications": {
"acctAuth": {
"accessToken": "2********8*********F"
}
}
}
Do we still need to use the Access_token?
08/20/2024 11:39 AM
You can keep as Bearer abcd
08/20/2024 11:28 AM
Postman is GET URL and Saviynt JSON says POST http method 🙂
08/20/2024 11:38 AM - edited 08/20/2024 11:40 AM
@rushikeshvartak
Both Get and Post work from Postman, and I Tried both from Saviynt.
Still the same error:
DEBUG-Got Webservice API Response: [headers:[Cache-Control: private, Content-Type: application/json; charset=utf-8, Server: Microsoft-IIS/10.0, jsonerror: true, X-AspNet-Version: 4.0.30319, X-Powered-By: ASP.NET, Date: Tue, 20 Aug 2024 18:35:31 GMT, Content-Length: 91], responseText:{"Message":"There was an error processing the request.","StackTrace":"","ExceptionType":""}, cookies:[], statusCode:500]
08/20/2024 11:42 AM
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"showResponse": true,
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=${account.accountID}",
"httpMethod": "POST","httpParams": {},
"httpHeaders": {
"Authorization": "${access_token}",
"X-Auth-Token": "2****8*****F",
"Accept": "application/json"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
201,
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
401,
400,
403,
404,
405,
409,
502
]
}
}
]
}
08/20/2024 11:56 AM
@rushikeshvartak
Still the same:
Got Webservice API Response: [headers:[Cache-Control: private, Content-Type: application/json; charset=utf-8, Server: Microsoft-IIS/10.0, jsonerror: true, X-AspNet-Version: 4.0.30319, X-Powered-By: ASP.NET, Date: Tue, 20 Aug 2024 18:55:26 GMT, Content-Length: 91], responseText:{"Message":"There was an error processing the request.","StackTrace":"","ExceptionType":""}, cookies:[], statusCode:500]
08/20/2024 12:02 PM
Share logs in text file
08/20/2024 12:31 PM
08/20/2024 02:45 PM
Are you sure POST works ?
else try with GETWITHBODY
08/20/2024 07:38 PM
@GPS
Based on the log, I think the parameters are missing in the JSON.
"httpParams": "{}",
or
"httpParams": "",
or
"httpParams": {},
{
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://uat-cloud.net/rightAngle/PFJ/CustomServices/PFJSecurityService.asmx/DisableUser?userName=${account.accountID}",
"httpMethod": "POST",
"httpParams": "{}",
"httpHeaders": {
"X-Auth-Token": "2****8*****F",
"Accept": "application/json"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
201,
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
401,
400,
403,
404,
405,
409,
502
]
}
}
]
}