Classic Universal Login page should give an error when using bad params

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.

Hi @cmcgowan!

Thank you again for taking the time to report this issue and for your patience while we investigated further with our Engineering team. At this time, the fix for this issue is in our Engineering team’s backlog, however, I am currently unable to provide an ETA on when the fix will be available. I understand the confusion that this issue caused and want to assure you that we are working to provide a fix as soon as possible.

Thank you for choosing Auth0!

1 Like

Thanks @Ale, it is a fairly minor issue so I appreciate your help throughout.

1 Like

No worries! We’re here for you!