Hi,
I have a webservice connector configured in IdentityNow and when I tried to do account provisioning, got the below error, also the userID is somethng auto generated in the target system so didn’t add the attribute in the create account provsioning plan, refer the screenshots below, what am I missing here?
Hi @ssel
Configuration looks correct. My assumption is that your response mapping is not correct. Could you show us a sample response from the create account endpoint as well as showing your config in the “Response Information” section.
You got $.User for the Root Path, but there is no User key in the response json. Try with just $ in the root path
I just noticed and tried that, no luck however thank you for pointing it out
Is the account created in the end system during this failed provisioning?
no getting the below error now,
[ConnectorError] Account create failed. Request failed with status code 500 (requestId: 75617efb0fbc4afd8e65a4fb249c7697)
Hi @ssel ,
So, the account creation itself is failing all the time? If not, you can check the payload and connectivity to the target system. Regarding the response mapping issue, I see you are using the UserId as (account name & account ID), which is calculated outside of SailPoint causing the issue. So, see if you have any other attribute that can be used as accountId or accountname (for ex, mail). This resolves the Native Identity issue.
Regards,
Karthi
Seems like the issue is with end system returning 500 error. It’s always a good practice to mention the Success Codes under Response information section for which you can use 2** as Success codes are usually 200 series, and ISC will show error when Status code is anything outside this range helping you trace the error easily
in body can you pass static value and do provisioning check whether it is working or not
Thank you All, everyone’s input is very helpful! And it’s started working after fixing the response information.
