When parametrized job's build URL is triggered by anonymous user with read permission only, Jenkins does not force this user to log in first and shows the parameters form. But when parameters are entered and the form is submitted, it navigates to the log in form, and finally, when the user is authorized, Jenkins navigates to the parameters form again with all data reset.

I believe that the right behavior will be to not to show the parameters form until user is logged in.