#8878: Authentication in the admin should not make any assumptions on valid user
names
--------------------------------------+-------------------------------------
Reporter: jdetaeye | Owner: nobody
Status: closed | Milestone:
Component: Admin interface | Version: SVN
Resolution: duplicate | Keywords: authentication
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
--------------------------------------+-------------------------------------
Comment (by jdetaeye):
Replying to [comment:1 ubernostrum]:
> Duplicate of #8342 and #7591. In the future, please search for existing
tickets before filing a new one.
Sorry about not having searched well enough for an existing ticket.
However, I don't agree with the resolution on the duplicate (and closed)
tickets. In this case it is 100% clear that the admin application is doing
tasks which are clearly outside it's domain. It violates the design of
truely pluggable authentication backends.
The argumentation used to close these tickets is flaky...
--
Ticket URL: <http://code.djangoproject.com/ticket/8878#comment:2>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---