Apparently on our client authorization page where we had Accept/Deny buttons, deny button was never working properly.
Instead of acting as a dumb link and redirect user to the failure url via GET request, it was submitting the form with blank POST body and cause identity to respond with an unrelevant error.
This change makes it behave like intended. I also made sure that the page looks exactly the same with that change.
Apparently on our client authorization page where we had Accept/Deny buttons, deny button was never working properly.
Instead of acting as a dumb link and redirect user to the failure url via GET request, it was submitting the form with blank POST body and cause identity to respond with an unrelevant error.
This change makes it behave like intended. I also made sure that the page looks exactly the same with that change.