#2550: [patch] Allow a Backend to Globally Fail Authentication
-------------------------------------+-------------------------------------
Reporter: umbrae@… | Owner: aashu_dwivedi
Type: New | Status: new
feature | Component: contrib.auth
Milestone: 1.4 | Severity: Normal
Version: SVN | Keywords: authentication
Resolution: | backends easy-pickings
Triage Stage: Design | Has patch: 1
decision needed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 1
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by dan.julius@…):
* needs_better_patch: 1 => 0
* ui_ux: => 0
* stage: Accepted => Design decision needed
Comment:
Modified PermissionDeniedBackend class:
- Set supports_anonymous_user and supports_object_permissions to True
- Added supports_inactive_user = True (which will be required in v1.5)
Implementing similar functionality for permissions will require design
change regarding get_all_permissions.
Since each backend provides a list of permissions it allows, the list
would be inconsistent if a backend raised the PermissionDenied exception
on a permission already in the list.
--
Ticket URL: <https://code.djangoproject.com/ticket/2550#comment:20>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
