#20218: Default authorization backend returns False when queried for object
level
permissions
------------------------------+----------------------------------------
Reporter: soren@… | Owner: Mehmet Dogan
Type: Bug | Status: assigned
Component: contrib.auth | Version: master
Severity: Normal | Resolution:
Keywords: auth | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------+----------------------------------------
Comment (by astandley):
I've gone back and forth on this issue, especially after reviewing all the
links Carlton has posted pertaining to it. I think at this point my
favored solution is the one proposed on ticket 13539 of adding a
`DefaultObjPermsBackend`, and setting it as part of the
`AUTHENTICATION_BACKEND` defaults. It combines some of the best aspects of
options 1, 2, and 3.
-It minimizes BC issues. Only installations which do not specify the
setting are effected. Migration/Depreciation warnings could be handled in
`django.conf.__init__`
-It changes the new default behavior of `user.has_perm(perm, obj)` to
return True as expected.
-It allows users a choice in behavior.
-It offers a documented example of model/object permission backends
working together.
--
Ticket URL: <https://code.djangoproject.com/ticket/20218#comment:18>
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/075.8ab06d312d7970c8103b4c79fd43f542%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
