You can press the login button multiple times, although no new session is created, this may cause problems in the future. There needs to be some sort of functionality that disables the button after the first click until the response from the server is received. If the login was a success, then we just redirect to the (currently nonexistent) dashboard, if it is a failure, a message will show up in the client that explains why the login was unsuccessful, the button is once again enabled. The button shouldn't just be disabled, but the function that the button executes should also be disabled to prevent users from executing this function in the developer console.
You can press the login button multiple times, although no new session is created, this may cause problems in the future. There needs to be some sort of functionality that disables the button after the first click until the response from the server is received. If the login was a success, then we just redirect to the (currently nonexistent) dashboard, if it is a failure, a message will show up in the client that explains why the login was unsuccessful, the button is once again enabled. The button shouldn't just be disabled, but the function that the button executes should also be disabled to prevent users from executing this function in the developer console.