#33231: authenticate() doesn't raise ImproperlyConfigured for incorrect
authentication backends.
-------------------------------------+-------------------------------------
Reporter: JunKi Yoon | Owner: JunKi
| Yoon
Type: New feature | Status: closed
Component: contrib.auth | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: authenticate, | Triage Stage:
AUTHENTICATION_BACKENDS | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by JunKi Yoon):
Replying to [comment:1 Mariusz Felisiak]:
> Django supports authentication backends with different set of
credentials, so they can have `authenticate()` methods with different
signatures. For example:
> - `authenticate(self, request, token=None)` and
> - `authenticate(self, request, username=None, password=None)`
>
> once you can call it with a `token` and once with an
`username`/`password`. Both calls are valid. That's why `TypeError` must
be ignored (see also #31968).
> Thanks for the detailed reply. I completely understand.
Have a good day:)
--
Ticket URL: <https://code.djangoproject.com/ticket/33231#comment:2>
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/065.9edda4718d25ccf974d9ef6ee2889d7d%40djangoproject.com.
