#24910: createsuperuser in interactive mode assumes USERNAME_FIELD is unique
----------------------------------------+------------------------
Reporter: carljm | Owner: nobody
Type: Bug | Status: new
Component: contrib.auth | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
----------------------------------------+------------------------
The checks framework allows for the possibility that you have a custom
User model with a non-unique `USERNAME_FIELD`, as long as you're using a
custom authentication backend that's able to handle that situation. But
the `createsuperuser` management command (in interactive mode) always
queries to see if the username you enter is already in use, and won't let
you proceed if it is.
Instead, `createsuperuser` should check whether `USERNAME_FIELD` is
actually a unique field, and only do the check if it is.
--
Ticket URL: <https://code.djangoproject.com/ticket/24910>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.af4cc2060511de9599205a3e0eaaccfc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
