Exchange - Rest Account Provisioning Task is getting failed.

[jbaskaran]

Hi All,

We are using a Rest connector to provision an Exchange account, but task is failing.

Initially task was successful with the success msg but account was in Inactive status. Later modified the JSON by referring the forum but now Task is getting failed with an error message "{"_id":"systemUserName"}.

Please find the below CreateAccountJSON when Task was successful but Account in InActive status :

{
"accountIdPath": "accountName",
"responseColsToPropsMap": {},
"call": [{
"name": "call1",
"connection": "entAuth",
"url": "https://xxxxxxxxxxx/Saviynt/PS/ExecutePSScript",
"httpMethod": "POST",
"httpParams": "{\"Script\": \"cd C:\\\\\\\\Scripts;.\\\\\\\\new-onid-user-setup-dev.ps1 -username ${user.systemUserName} -primaryAffiliation ${user.customproperty30}\"}",
"httpHeaders": {
"Authorization": ""
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"statusCode": [
200,
201,
204,
205
]
},
"unsuccessResponses": {
"statusCode": [
500
]
}
}]
}

Modified JSON after referring the FORUM but task is getting failed:

{
"accountIdPath": "accountName",
"responseColsToPropsMap": {},
"call": [{
"name": "call1",
"connection": "entAuth",
"url": "https://test-psconnect.greenforest.sig.oregonstate.edu/SaviyntApp/PS/ExecutePSScript",
"httpMethod": "POST",
"httpParams": "{\"Script\": \"Powershell.exe C:\/Scripts\/new-onid-user-setup-dev.ps1 '${user.systemUserName}' '${user.customproperty30}'\"}",
"httpHeaders": {
"Authorization": "${access_token}"
},
"httpContentType": "application/x-www-form-urlencoded",
"successResponses": {
"response[9].Objectreturned": ["Success"]
},
"unsuccessResponses": {
"response[9].Objectreturned": ["Failure"]
}
}]
}

Request you to please help me in fixing the same.

Thanks

[SB]

Can you update ConfigJSON param in the REST connection with value {"showLogs":true} if not done already and share the logs. Use the JSON with which task was successful but the status was inactive.

[rushikeshvartak]

Can you try systemusername in lowercase