REST Connector - Provisioning Comments not shown incase of 500 , 400 error codes

[IAM_99]

Hi All,

Incase of Provisioning failed its because of 500, 400 error - its not showing ProvisioningComments, we have to check in the logs.

any idea - how to configure/show  that exception at Provisioning Comments level  ?

Thanks,

suresh

[khalidakhter]

@IAM_99 

Have you observed this issue in all the provisioning use cases or with a particular task type?

[IAM_99]

Hi @khalidakhter Its happening all REST Connector/apps ( if 500, 400  exception we need to check in logs only as provisioing comments is not capturing this ).

Thanks,

suresh

[khalidakhter]

Hi @IAM_99 

I tried for the New Account use case and I can see the provisioning comments stored in the task details. The same can be seen in the below snippet.

Can you please explain a bit more on which specific use-case the Provisioning Comments are not getting stored?

[IAM_99]

Hi @khalidakhter ,

We are creating an Account ( New Account) below is my  CreateAccountJSON JSON code, any thing to be added ?

{
"accountIdPath": "call1.message.userName",
"call": [{
"name": "call1",
"connection": "userAuth",
"httpMethod": "POST",
"url": "https://xxxxxxxxxxxxxxxxxxx/users",
"httpParams": "{\"firstName\":\"${user.firstname}\",\"lastName\":\"${user.lastname}\",\"email1\":\"${user.email}\",\"regions\":\"${requestAccessAttributes.get('regions')}\"}",
"httpHeaders": {
"Authorization": "${access_token}",
"Accept": "application/json"
},
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200,
201,
202,
203,
204
]
}

}]
}

thanks,

suresh

[Manu269]

Ideally Provisioning comments fetches the response post operation.

There are a few applications where you get same status code for both successful and unsuccessful API calls. In that case, you can handle the tasks status in IGA based on the API response body content.

Sample example :

{
"httpContentType": "application/json",
"successResponses": {
"statusCode": [
200
]
},
"unsuccessResponses": {
"response.StatusCode": "1"
}
}

[khalidakhter]

@IAM_99 

The shared JSON must work as expected and comments should get captured in case of any failure. Can you please share a sample message that API returns for 500 or 400 error codes? Also, mention your ECM version as well.

[IAM_99]

Hi @khalidakhter @Manu269  ,

please find below 

From the logs

\"message\":{\"error\":\"User with same email exists\",\"code\":400},\"statusCode\":400,\"description\":null,\"status\":\"Failed\"}}\n","stream":"stdout","time":"2023-07-03T13:25:10.549418365Z"}

Thanks,

suresh

[rushikeshvartak]

try below json

{
  "accountIdPath": "call1.message.userName",
  "call": [
    {
      "name": "call1",
      "connection": "userAuth",
      "httpMethod": "POST",
      "url": "https://xxxxxxxxxxxxxxxxxxx/users",
      "httpParams": "{\"firstName\":\"${user.firstname}\",\"lastName\":\"${user.lastname}\",\"email1\":\"${user.email}\",\"regions\":\"${requestAccessAttributes.get('regions')}\"}",
      "httpHeaders": {
        "Authorization": "${access_token}",
        "Accept": "application/json"
      },
      "httpContentType": "application/json",
      "successResponses": {
        "statusCode": [
          200,
          201,
          202,
          203,
          204
        ]
      },
      "unsuccessResponses": {
        "statusCode": [
          400,
          403,
          401,
          404,
          409,
          501,
          500
        ]
      }
    }
  ]
}

[IAM_99]

Hi @rushikeshvartak  tried above error codes , but its not showing in provision comments, we have search logs for actual error. any other inputs ?

Thanks,

suresh

[rushikeshvartak]

Does it shows when you check from Postman

[IAM_99]

Yes it shows ( like in logs)

[rushikeshvartak]

Currently v23.6 i can see error is visible. It seems version issue