I am building identity layer in my app using AAD B2C. I got across very unpleasant behavior of the service. If there is a certain internal error, it responds with the page with only raw text in it: Bad request. I do not need help figuring out what causes the error (in my case it is the fact, that facebook UI allows multiple submissions in consent window which fires multiple callbacks to AAD B2C, which can't handle that).
I am looking for a solution to prevent this Bad Request page being displayed to the user whatsoever, even in case error happens. This is highly undesirable behavior of the service. It should be capable to at least redirect back to my application and not hang up on b2clogin domain with raw Bad Request message.
My issue differes from what is mentioned in this question from SO: B2C Custom Policy - Redirect login error back to app as I am not forwarded to api error page. I receive generic bad request response. The reason for getting the error as I mentioned is multi submit of Facebook login prompt.
