Wt

Hey,

I've done some refactoring in the Auth module: there is now an AuthModel, just as there was a RegistrationModel, which encapsulates the authentication logic.

So, back to your original question: you can either specialize the model, or the view, to avoid indicating which fields (user name / password) are invalid, in case the model does not validate. But, I still have doubts on how to handle attempt throttling in that case. And are there not many other ways to know if a certain user is already registered, for example when choosing a user name in the registration form you will have to indicate that that user is already registered?

Regards,

koen

Fixed in 3.2.1