Is this not a possible scenario you can detect and notify the user of in some way? I first logged in multiple times, cleared cookies, tried incognito before finally having to google and find the community post explaining the cause.
This was quite a bad experience for a product who’s main business is centered around that login page. The only hint I got was that in a fresh instance after logging in once the text went to “log in to Auth0” to “log in to team***”, after that it just loops with not indication why I am not getting into that team, as my details were correct.
I have moved your post from the Product Feedback page to the Get Help category due to the following reasons:
I understand that this kind of UX can be frustrating, however, it is a design choice in which the user is provided an ambiguous message just like in the default customization of the UL.
This takes into consideration scenarios like brute force attempts where it is stated that “The username or password is incorrect” and not exact errors like “Username does not exist” or “Password is incorrect”.
Support for this kind of issues is available through our support site in the following knowledge articles: