So I am using the new universal login with customised login page. Everything works fine unless I try to login with a user that has been blocked (via the Auth0 User Interface, User Management → Users).
When I login with a blocked user the login page reloads, as if it were going to load the app, then immediatele reloads the Auth0 login page with no error message dispalyers or in the URL. Im pretty sure the app isnt loading at all because the backend isnt being called which it would be if it loaded, so its just Auth0 reloading the page and not displaying an error.
Is this normal behaviour for Auth0 blocked users, and if so is there anyway I can just have it display an error message (such as if an incorect email or password were supplied)?
That does not seem to be the expected behaviour for a blocked user. Usually, if an user is blocked, by testing the login experience via the Dashboard, you should be redirected to a page where it displays that the user is blocked.
I have tested this with a sample application as well and the user is redirected to a page which states: Oops... user is blocked. In this situation, you application should handle redirection of the user since they will be blocked access to either a custom error page or via a prompt on your main page. Otherwise, the login page should redirect the user to such a screen unless your application is not configured to handle the behaviour.
As an alternative solution, instead of blocking the user inside the dashboard, you could assign metadata to them which stated they are being blocked and once they attempt to log in, via an Action Trigger, log them out and display a custom message.