Opened 10 years ago

Closed 10 years ago

#2083 closed defect (wontfix)

Why is the username field in "django/contrib/auth/" restricted?

Reported by:… Owned by: Adrian Holovaty
Component: Contrib apps Version: master
Severity: minor Keywords: username auth
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


Why is the username field for a user in django restricted to: 30 chars, alphanumeric?

It is more use to everybody who wants to be "more open" with his site when the username can be (nearly) anything. Let the site-creator decide (using his own validators) how the username should look like for his site.


username = models.CharField(_('username'), maxlength=30, unique=True, validator_list=[validators.isAlphaNumeric])

should be changed to something like:

username = models.CharField(_('username'), maxlength=255, unique=True)

Regards, Alex

Change History (2)

comment:1 Changed 10 years ago by Adrian Holovaty

Component: Core frameworkContrib apps
priority: normallow
Severity: normalminor

It's restricted like that because that's how we liked to validate our usernames at World Online.

comment:2 Changed 10 years ago by Adrian Holovaty

Resolution: wontfix
Status: newclosed

If you don't like this behavior, you can use a custom auth backend. See the new docs.

Note: See TracTickets for help on using tickets.
Back to Top