Web Services Connector Validating Return Response

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Using a Direct Connection Web Service source to connect to a Create Account endpoint. The return response has an attribute IsValid that under certain circumstances can be set to False if the end point was unsuccessful in creating the account but the HTTP POST process still returns a 200. This might occur if the process is executed to create a new account using a unique identifier that is already in use for another account.

Currently the HTTP Operation Success Code is set to 2** but this means that the process is “creating” the account in ISC which is not good. I can log an error in a WebServices After Operation rule by checking for that IsValid attribute but I would prefer to do something along the lines of failing the process so ISC does not create that account.

Could anyone suggest a best practice for how this should be handled and an overview of how it would be implemented? Thanks.

2

you can throw exception in after operation rule, check this isValid attribute and throw exception also in additional settings of the connector enable throw exception in after operation

1 Like
3

Use a Before Operation Rule to do a pre-check. But if you’re relying solely on the response from Create Account, then After Operation + Exception to check if the attribute is valid is the most reliable solution.

2 Likes