ISC Workflows » HTTP Request » OAuth 2 errors not reported when token endpoint fails

Feedback Bugs
,
1

What problem are you observing?

Errors and output are hidden from the implementer, proper error handling is not present in the HTTP Request Action.

For the HTTP Request action you must configure two endpoints when using the “OAuth 2.0 - Client Credentials Grant”:

  • Token URL
  • Request URL

If the Token URL returns an error:

  • 4xx response error, or
  • the access_token is not present in the JSON response

the Workflow Action will continue with an empty Bearer token.
The Request URL will receive such an HTTP header: Authorization: Bearer.

The implementer doesn’t know that the first request has failed.

What is the correct behavior?

Proper error handling and debugging capabilities should be implemented in the HTTP Request action.

The workflow should error out and point out to the error, instead of proceeding to the calling the Request URL with an empty Bearer token.

What product feature is this related to?

ISC Workflows » HTTP Request Action

What are the steps to reproduce the issue?

  • Create a workflow with an HTTP action
  • Use an URL for the Token URL that returns a similar response:
HTTP/1.1 400 400
Content-Type: application/json;charset=UTF-8

{"error_description":"xxx","error":"invalid_request"}
  • Test the workflow and see that this error doesn’t prevent the workflow to continue

Do you have any other information about your environment that may help?

No