Announcing the Saviynt Knowledge Exchange unifying the Saviynt forums, documentation, training,
and more in a single search tool across platforms. Read the announcement here.

Create account JSON not working for REST connector

Murari
New Contributor II
New Contributor II

Hi Team,

Getting below error when passing FirstName and Email params in create account JSON.

JSON-

Murari_0-1705998790524.png

Error-

Murari_1-1705999272206.png

If I am passing hardcoded value for email then it is working as expected.

Please suggest.

Thanks,

Hare Murari

 

15 REPLIES 15

rushikeshvartak
All-Star
All-Star

Share full json

change user.FirstName to {user?.firstname}

{user?.email}


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi Rushikesh,

I have tried the json suggested by you above but still getting the same error-

Murari_0-1706074210864.png

Please find complete JSON below-

{
"accountIdPath": "call1.message.id",
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://domain/user/2/Ac6AzcKIGF7y/",
"httpMethod": "POST",
"httpParams": "{\"FirstName\": \"${user?.FirstName}\", \"Email\": \"${user?.email}\", \"Kind\": \"${requestAccessAttributes.get('Kind')}\"}",
"httpHeaders": {
"X-Access-Key-Id": "",
"X-Access-Key-Secret": "",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201
]
}
}
]
}

Thanks

{
"accountIdPath": "call1.message.id",
"call": [
{
"name": "call1",
"connection": "acctAuth",
"url": "https://domain/user/2/Ac6AzcKIGF7y/",
"httpMethod": "POST",
"httpParams": "{\"FirstName\": \"${user?.firstname}\", \"Email\": \"${user?.email}\", \"Kind\": \"${requestAccessAttributes.get('Kind')}\"}",
"httpHeaders": {
"X-Access-Key-Id": "",
"X-Access-Key-Secret": "",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201
]
}
}
]
}


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi Rushikesh,

I have tried the above JSON suggested by you but still no luck.

Murari_0-1706499344856.png

Thanks

Hare Murari

Share postman working screenshot and saviynt logs by enabling logs to validate parameters getting sent 


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Hi Rushikesh,

Please find the Postman screenshot and Saviynt logs below-

Murari_0-1706836873363.pngMurari_1-1706837031378.png

 

Thanks

Hare Murari

Does your email from saviynt ends with @maxis.com.my


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Yes.

Murari_0-1706855489356.png

Thanks,

Murari

share logs in file


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Please find the attached logs.

Regards,

Murari

Manu269
All-Star
All-Star

Can you try below :

For Firstname : {user?.firstname}

Email : {user?.email}

Regards
Manish Kumar
If the response answered your query, please Accept As Solution and Kudos
.

Murari
New Contributor II
New Contributor II

Hi Manu,

Hi Rushikesh,

I have tried the json suggested by you above but still getting the same error-

Murari_1-1706074395505.png

Thanks

 

NM
Regular Contributor III
Regular Contributor III

Hi Murari,

We had the same issue for one of the application, Could you please check the email format required on application end(Restriction).. is it matching to what is been send from saviynt.

Murari
New Contributor II
New Contributor II

Hi NM,

I have checked it with app team there is no such restriction at their end. When we are passing the hardcoded value for same emailid it is working as expected.

Regards,

Hare Murari 

AmitM
Valued Contributor
Valued Contributor

Hi @Murari ,

Can you move your email to another attribute lets say cp1 and use ${user.customproperty1}. Just to eliminate whether its value issue or attribute issue.

Also if you could make showLogs=true in configJSON and share

{
"connectionTimeoutConfig": {
"connectionTimeout": 10,
"readTimeout": 60,
"writeTimeout": 60,
"retryWait": 2,
"retryCount": 3

},
"showLogs": true
}