[GH-ISSUE #210] Allow email login #188

New issue

Closed

opened 2026-02-26 09:36:25 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:36:25 +03:00

Owner

Originally created by @perguth on GitHub (Jun 15, 2015).
Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/210

Chrome expects the default login to be the email address (respectively does not recognize that nsupdate wants to have it differently).

To reproduce:

Go to nsupdate.info
Create a useraccount.
Allow Chrome to save the password.
Click on the email link and go to the loginpage.
The then presented credentials set the email address as username which will fail.

Originally created by @perguth on GitHub (Jun 15, 2015). Original GitHub issue: https://github.com/nsupdate-info/nsupdate.info/issues/210 Chrome expects the default login to be the email address (respectively does not recognize that nsupdate wants to have it differently). To reproduce: 1. Go to nsupdate.info 2. Create a useraccount. 3. Allow Chrome to save the password. 4. Click on the email link and go to the loginpage. 5. The then presented credentials set the email address as username which will fail.

kerem

2026-02-26 09:36:25 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 09:36:26 +03:00

Author

Owner

@izaim commented on GitHub (Sep 8, 2015):

I had this problem too, opened and closed an issue about this because yours is more detailed. Hope they improve that, thanks.

@izaim commented on GitHub (Sep 8, 2015): I had this problem too, opened and closed an issue about this because yours is more detailed. Hope they improve that, thanks.

kerem commented

2026-02-26 09:36:26 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Dec 28, 2015):

The code evaluating that form's content is in django.contrib.auth.views.login (so, it is not our code).

Also, I find it a bit stupid that chrome behaves that way, esp. since the form id / label does not say anything about "mail" or "email", but about "username".

@ThomasWaldmann commented on GitHub (Dec 28, 2015): The code evaluating that form's content is in `django.contrib.auth.views.login` (so, it is not our code). Also, I find it a bit stupid that chrome behaves that way, esp. since the form id / label does not say anything about "mail" or "email", but about "username".

kerem commented

2026-02-26 09:36:26 +03:00

Author

Owner

@ThomasWaldmann commented on GitHub (Apr 17, 2023):

One can use the email address also as username for the service, so guess that solves it.

@ThomasWaldmann commented on GitHub (Apr 17, 2023): One can use the email address also as username for the service, so guess that solves it.