connector_possibleHttpErrors

Identity Security Cloud (ISC) ISC Discussion and Questions
1

I have a web service which will return a 200 status, even though the update may fail.

I saw connector_possibleHttpErrors mentioned in the documentation:
https://documentation.sailpoint.com/connectors/webservices/help/integrating_webservices/additional_configuration_parameters.html?Highlight=connector_possibleHttpErrors
But I’m not sure how to configure it for my situation.
A successful call returns:

<user-batch-result xmlns="http://www.ZZZZZ.com/api/user/2011/02" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
    <records-succeeded>1</records-succeeded>
    <records-failed>0</records-failed>
    <UsersDetails>
        <UserInfo>
            <EmployeeID>171471</EmployeeID>
            <FeedRecordNumber>1</FeedRecordNumber>
            <Status>SUCCESS</Status>
        </UserInfo>
    </UsersDetails>
</user-batch-result>

And a failed call returns:

<user-batch-result xmlns="http://www.ZZZZZ.com/api/user/2011/02" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
    <records-succeeded>0</records-succeeded>
    <records-failed>1</records-failed>
    <errors>
        <error>
            <FeedRecordNumber>1</FeedRecordNumber>
            <message>Missing Required Field: EmpId</message>
        </error>
    </errors>
    <UsersDetails/>
</user-batch-result>

So the failed call returns a set of data. I’m not sure what I should use for the value for the connector_possibleHttpErrors key. I tried “errors”, but that didn’t work.

Or is there a way to use the records-succeeded record?

Any thoughts?

Thanks,
Chris

2

Hey Chris,
The format of connector_possibleHttpErrors is this:
{“errorCodes”:[204,200],
“errorMessages”:[“Testing”,“Not Found”]
}

This means whatever error code you are getting when there is failure you can put those codes in errorCodes list. The error messages part is interesting. Connector searches whole response body using the strings provided in here and whenever it sees that string it marks it as failure. The comparison of errorMessages is only done when we get any of the errorCodes in response.

P.S. This looks like concur and you are using old apis which are not reliable. Try to get hands on latest one which I believe is v4 and setup connector using that. Sharing this from personal experience

1 Like