-
Bug
-
Resolution: Done
-
Minor
-
None
-
2.1 GA, SaaS
-
3scale 2019-12-09, 3scale 2019-12-23, 3scale 2020-01-13, 3scale 2020-02-03
When the regenerate secret button is clicked twice in succession very quickly the response is a 404 Not Found. Based on the way this currently works it's actually expected because the client_secret value has not yet been regenerated at the moment the second request happens and therefore is sent in the request.
However, what is unexpected is the fact the Error Layout is rendered on top of the current view.
Dev notes
We should use disable_with on the submit button