Feature: Classical Universal Login will not give an error if you hit the
/login route with bad parameters. It would be better if it did (New Universal Login already has this behavior).
Description: This is an edge case for Classic UL where I’d expect to get an error but did not. It applies when you have not set up a tenant-level Default Login Route
More details can be found in this topic I already posted Classic Universal Login (/login) page returns 200 when given junk parameters
Use-case: A user tripped on this edge case and raised a support ticket with us. The situation was hard to debug for us. If there was an error message it could have helped our dev team debug, or even helped our user realize their mistake on their own.