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

Createaccount JSON not working- Rest based

SESH
New Contributor
New Contributor

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
]
}
}
]
}

13 REPLIES 13

naveenss
All-Star
All-Star

@SESH is this working from postman? Please share the working request from postman with curl. 

Regards,
Naveen Sakleshpur
If this reply answered your question, please click the Accept As Solution button to help future users who may have a similar problem.

SESH
New Contributor
New Contributor

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"
}

 

NM
Honored Contributor III
Honored Contributor III

@SESH user.manager.username isn't the right variable.


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

SESH
New Contributor
New Contributor

Can you please let me know the right variable that should be used here

NM
Honored Contributor III
Honored Contributor III

@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


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'

rushikeshvartak
All-Star
All-Star
{
  "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]
      }
    }
  ]
}

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

This did not work either. Looks like the connection JSON isn't working too now. Import user resulted in an error.

 

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.


Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

I have attached the logs file in text format.

stalluri
Valued Contributor II
Valued Contributor II

@SESH 

Can you share the log in Text file. Make sure the below is same in connection and createaccount.

"connection": "acctAuth",

 


Best Regards,
Sam Talluri
If you find this a helpful response, kindly consider selecting Accept As Solution and clicking on the kudos button.

SESH
New Contributor
New Contributor

acctAuth is same in connection and createaccount. Attached are the logs in text format,

  • Please share connection JSON in text file.
  • Share postman screenshot of connection  auth and curl command
  • Please share postman screenshot and 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.‼️‼️⚠️

Regards,
Rushikesh Vartak
If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'.

NM
Honored Contributor III
Honored Contributor III

@SESH is there any change in creds by app team?


If this helped you move forward, click 'Kudos'. If it solved your query, select 'Accept As Solution'