HTTP ERROR 500 when wrong Hub-ID is provided when initiating an OAuth integration (using OAuth1.0)



When initiating an OAuth1.0 connection, if we pass a wrong (or invalid) Hub-Id in the url, we are getting a below error page:

Is there any way to gracefully handle this scenario with a proper redirection rather than throwing a 500 ERROR so that we can handle the failure from our end?


@Venu_Bandaru upon receiving the response code >= 500 you could write in a redirect. However that all being said we’ll be shutting down our OAuth1 system on Friday, August 11th, 2017 so you might want to spend some time if you can moving over to OAuth2. Due to the fact that we are shutting down OAuth1 in a month we will not be making any server-side changes to it.