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

Task is getting failed, due to wrong value getting passed.

IAM-Vaibhav
New Contributor III
New Contributor III
Hi team ,
 
I am unable to see values going to end application in add access call due to that I am not able identify the issue with values being sent to application and add access request is getting errored out.
 
 
After API called below response is received and application team is asking us to check the values being sent to application while calling Api. I can see only below message in debug logs after Api call not able to see call details [which has actual values] before making call.
"Project":{"headers":"4SBdv6aSyyAqhBgNrVNyJ+yaBFCVP3uoZOqjiyjsDbs7W5cbTdF+ojnQqXgZY3kVb4v707CmT/4hSuGBkfAuseH1N9JMG8UDHG5FKI3XUmWKdQgxgIt0Wp26VOkD/bSJ","message":{"data":[],"message":["Server Error, contact the system administrator referencing this error code: ABB-E06EDC1641"],"status":500},"statusCode":200,"description":null,"status":"Success"}} 
 
attached debug log file. Search for this thread: 2023-12-13/11:30:23.919 [{}] [quartzScheduler_Worker-9]  DEBUG rest.RestProvisioningService - in reinitializeAddAndRemoveAccessJson
 
Add Access JSON :
--------------------------
{
"call": [
{
"name": "Project",
"connection": "acctAuth",
"url": "https://<HOSTNAME>/ws/rest/service/v1/admin/user/shell/membership",
"httpMethod": "PUT",
"httpparams": "{\"shellnumber\": \"${entitlementValue.customproperty6}\",\"users\": [{\"username\": \"${user.email}\",\"group_add\":\"${if (requestAccessAttributes?.get('groups')!=null){requestAccessAttributes?.get('groups')} else{\"\"}}\"}]}",
"httpHeaders": {
"Authorization": "${access_token}",
"contentType": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
400,
401,
403
]
}
}
]
}
13 REPLIES 13

IAM-Vaibhav
New Contributor III
New Contributor III

Hi Team ,

Could you please update me on this.

regards,

VP. 

Hi @IAM-Vaibhav 

Can you update ConfigJSON param in the REST connection with value {"showLogs":true} if not done already. Run the job again and search for below string in the logs. You should be able to see if the attributes values are being passed in the required format.

Please refer Solved: Rest- RemoveAccessJson -- Getting 500 status code - Saviynt Forums - 34522

1. What is the provisioning comments?

2. Are you able to do the perform the same operation from postman ?

Regards,

Dhruv Sharma

Hi @Dhruv_Sharma ,

could you please check below and help to identify the issue. App team is saying there is error in values being sent to application. that why we are getting error and same has been shown in provisioning comments.

show Logs already enabled, 

I can see below provisioning comments in task :

"Project":{"headers":"4SBdv6aSyyAqhBgNrVNyJ+yaBFCVP3uoZOqjiyjsDbs7W5cbTdF+ojnQqXgZY3kVb4v707CmT/4hSuGBkfAuseH1N9JMG8UDHG5FKI3XUmWKdQgxgIt0Wp26VOkD/bSJ","message":{"data":[],"message":["Server Error, contact the system administrator referencing this error code: ABB-E06EDC1641"],"status":500},"statusCode":200,"description":null,"status":"Success"}} 

and I can able to execute it from postman.

Below are logs in debug log file, in this log I can't see values being sent to rest Api before call. Its just has response from API.

2023-12-13/11:30:23.029 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestProvisioningService - connection: acctAuth
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestProvisioningService - Inside pullObjectsByRest
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestUtilService - Got showLogs = true
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestProvisioningService - Calling Webservice Url - https://<Hostname>/ws/rest/service/v1/admin/user/shell/membership with httpParams - null
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - calling executeRequestWithTimeoutConfig for api...
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - calling api...
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - before calling executeRequestWithHeaders for api...
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - isFipsEnabled = false
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - getHttpClient - sslParams : null
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - getHttpClient - proxyParams : null
2023-12-13/11:30:23.142 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - getHttpClient - sslSocketFactory : null
2023-12-13/11:30:23.143 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - setting connection timeout to 120 seconds and request timeout to 60 seconds
2023-12-13/11:30:23.143 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - getHttpClient - HttpClientBuilder.create().build() called.
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - called executePutRequestWithHeaders for api...
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - after calling executeRequestWithHeaders for api...
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - called api...
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - timeout validated for api...
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG services.HttpClientUtilityService - got response for api...
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestUtilService - Got showLogs = true
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestProvisioningService - Got Webservice API Response: [headers:[Date: Wed, 13 Dec 2023 11:30:23 GMT, Content-Length: 153, Content-Type: text/plain], responseText:
{
"data":
[
],
"message":
[ "Server Error, contact the system administrator referencing this error code: ABB-EFEA6DFA26"
],
"status":500
}, cookies:[], statusCode:200]
2023-12-13/11:30:23.421 [{}] [quartzScheduler_Worker-9] DEBUG rest.RestUtilService - pullObjectsByRest - responseStatusCode ::200

 

regards ,

VP.

Hi @IAM-Vaibhav 

Please crosscheck the http params as it is being passed as null.

Calling Webservice Url - https://<Hostname>/ws/rest/service/v1/admin/user/shell/membership with httpParams - null

Regards,

Dhruv Sharma

IAM-Vaibhav
New Contributor III
New Contributor III

Hi @Dhruv_Sharma  ,

In JSON I have configured http params and syntax wise it is also correct . 

I tested by Passing static values as well. 

Could you please suggest other way to validate it. 

IAM-Vaibhav
New Contributor III
New Contributor III

Hi @Dhruv_Sharma  ,

Any update on this ?.

 

Hi @IAM-Vaibhav 

Could you please try the same with less parameters in the http params? Here you are passing shellnumber, users. Just try to pass only shell number and see if it works. This is to validate if the issue lies in if-else block.

"httpparams": "{\"shellnumber\": \"${entitlementValue.customproperty6}\",\"users\": [{\"username\": \"${user.email}\",\"group_add\":\"${if (requestAccessAttributes?.get('groups')!=null){requestAccessAttributes?.get('groups')} else{\"\"}}\"}]}"

Hi @IAM-Vaibhav 

Please let me know if you are able to get the results for the above scenario ?

Regards,

Dhruv Sharma

Hi @Dhruv_Sharma  ,

I was away, couldn't be able to reply here.

Request are getting processed now but still issue with values : Now I observed issue with 

shellnumber\": \"${entitlementValue.entitlementID} ,Do you see any error in below json. particularly in httpParams section

this is my current JSON :

{
"call": [
{
"name": "Project",
"connection": "acctAuth",
"url": "https://<Hostname>/ws/rest/service/v1/admin/user/shell/membership",
"httpMethod": "PUT",
"httpParams": "{\"shellnumber\": \"${entitlementValue.entitlementID}\",\"users\": [{\"username\": \"${user.email}\",\"status\": \"${if(user.status=1){return 'Active'}else{return'Inactive}'}\",\"group_add\":\"${if(requestAccessAttributes?.get('groups')!=null){requestAccessAttributes?.get('groups')}}\"}]}",
"httpHeaders": {
"Authorization": "${access_token}",
"contentType": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"statusCode": [
500,
400,
401,
403
]
}
}
]
}

This is API response :

{"Project":{"headers":"4SBdv6aSyyAqhBgNrVNyJyKjfO6XRgbTNSIKfMCDSg518PmvRyKoi+IGVuXYFI3g+YBIs7kJ6ST8EiytixkvsNlxPLl4Q3WBcyZ0fJBBk7arxTuuSiN/LzkLJ1sbSpw+","message":{"data":[],"message":["Project/Shell Number is not correct."],"status":602},"statusCode":200,"description":null,"status":"Success"}}.

 

Attaching Postman body and response for more reference.

IAMVaibhav_0-1703773717738.png

 

 

IAM-Vaibhav
New Contributor III
New Contributor III

Hi @Dhruv_Sharma ,

Can we have call to resolve this tomorrow as per your availability. 

regards,

VP.

Hi @IAM-Vaibhav 

From the error, it looks like shell number value is not as expected in the target application. Can you check if the value for entitlementValue.entitlementID for some users in Saviynt and see if it is as expected. Also please check if this value contains any special characters which need to be taken care in http params.

Regards,

Dhruv Sharma

KhalidAkhterIGA
New Contributor II
New Contributor II

Hi @IAM-Vaibhav 

I can see i the log that API is getting invoked with NULL parameter that means the Body parameter is getting excluded from API call.

It could be the issue with the syntax of parameter name httpparams. You can try with updating it as httpParams.

IAM-Vaibhav
New Contributor III
New Contributor III

Hi @KhalidAkhterIGA and @Dhruv_Sharma ,

Thanks for your reply . This has been resolved. 

@KhalidAkhterIGA As you mentioned, it was one of the issue.