#32181: ModelBackend used hardcoded global variable UserModel that cannot be
overrided.
-------------------------------------+-------------------------------------
Reporter: danilovmy | Owner: nobody
Type: New feature | Status: closed
Component: contrib.auth | Version: 3.1
Severity: Normal | Resolution: wontfix
Keywords: custombackend, | Triage Stage:
ModelBackend | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* easy: 1 => 0
* has_patch: 1 => 0
* type: Uncategorized => New feature
Comment:
I'm not really sure if I understand your use case. Do you have different
user models for different authorization backends? (because `ModelBackend`
supports a custom model for users). If so, it's fair that you need to
override `authenticate()` in such an advanced usage, IMO. We cannot
maintain hooks for all niche scenarios. You can start a discussion on
DevelopersMailingList if you don't agree.
--
Ticket URL: <https://code.djangoproject.com/ticket/32181#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f111ed48d8a25cee98beb9a394ab0d0c%40djangoproject.com.
