#25057: Permission for view (CRUD) and correct handling of inactive users for
business applications
-------------------------------------+-------------------------------------
Reporter: djbaldey | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: contrib.auth | Version: master
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for the suggestions.
The request for a "view" permission is a duplicate of #820 which was
closed as "won't fix". If you want to reopen the discussion, please write
to the DevelopersMailingList.
I don't find your proposal for permissions checking compelling because
these ideas can be implemented with a custom user model. That seems more
elegant that requiring an application to pass `check_active=False`
everywhere it does permission checks. Also, the default `ModelBackend`
[https://github.com/django/django/blob/a570701e02e0bc09d977c8ae0b6ee987a1190039/django/contrib/auth/backends.py#L33-L40
doesn't return any permissions for inactive users] so that would need to
be overridden as well.
For future reference, please keep a ticket focused on one issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/25057#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 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/066.0b87f6da4df363be645f6a41a20a1a2a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
