Click HERE to see how Saviynt Intelligence is transforming the industry. |
10/15/2024 03:45 AM
CreateaccountJSON is not working for a rest based application we are working on. We used a similar syntax for connection JSON which is working fine for import accounts. Below is the createaccountJSON we are using. I have attached a screenshot from the logs.
{
"accountIdPath": "accountName",
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"httpMethod": "POST",
"httpParams": "{\"arguments\":{\"connectionID\":${access_token},\"user\":{\"active\": \"true\", \"userName\": \"${user.username}\", \"esigPassword\": \"${randompassword}\", \"firstName\": \"${user.firstname}\", \"lastName\":\"${user.lastname}\", \"supervisor\":\"${user.manager.username}\", \"password\": \"${password}\"}},\"methodName\":\"createUser\",\"serviceName\":\"UserService\"}",
"httpHeaders": {
"Accept": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"statusCode": [
400,
401,
404,
405,
500
]
}
}
]
}
10/15/2024 04:11 AM
@SESH is this working from postman? Please share the working request from postman with curl.
10/15/2024 05:14 AM
Hi Naveen,
This was working from Postman. Below is the sample of an example call.
{
"arguments":{
"connectionID":"(site share name)-(unique session ID)",
"user":{
"esigPassword":"123456",
"lastName":"Wayne",
"supervisor":"SYSADMIN",
"password":"QualityHero1!",
"firstName":"Bruce",
"userName":"BATMAN"
}
},
"methodName":"createUser",
"serviceName":"UserService"
}
10/15/2024 04:15 AM
@SESH user.manager.username isn't the right variable.
10/15/2024 05:11 AM
Can you please let me know the right variable that should be used here
10/15/2024 05:50 AM - edited 10/15/2024 06:02 AM
@SESH try this
${usermanager.username}
If not working you might have to store manager username in one of the custom property or have a DA
10/15/2024 06:44 AM
{
"accountIdPath": "accountName",
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://xxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
"httpMethod": "POST",
"httpParams": "{\"arguments\": {\"connectionID\": \"${access_token}\", \"user\": {\"active\": \"true\", \"userName\": \"${user.username}\", \"esigPassword\": \"${randompassword}\", \"firstName\": \"${user.firstname}\", \"lastName\": \"${user.lastname}\", \"supervisor\": \"${usersManagerObj?.username}\", \"password\": \"${password}\"}}, \"methodName\": \"createUser\", \"serviceName\": \"UserService\"}",
"httpHeaders": {
"Accept": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [200]
},
"unsuccessResponses": {
"statusCode": [400, 401, 404, 405, 500]
}
}
]
}
10/16/2024 11:04 AM - edited 10/16/2024 11:08 AM
This did not work either. Looks like the connection JSON isn't working too now. Import user resulted in an error.
10/16/2024 11:05 AM
Please share the logs in text format for easier debugging. Additionally, provide the task ID, error details, or specific line numbers where the issues occur to help us review the relevant sections efficiently.
⚠️ Important: Do not upload attachments containing sensitive information, such as IP addresses, URLs, company/employee names, or email addresses. For more information, refer to the Saviynt PII Policy.
10/21/2024 01:27 AM
10/16/2024 07:46 PM
@SESH
Can you share the log in Text file. Make sure the below is same in connection and createaccount.
"connection": "acctAuth",
10/21/2024 01:29 AM
10/16/2024 08:34 PM - edited 10/16/2024 08:34 PM
@SESH is there any change in creds by app team?