#17430: Clearly document the permissions model for the Django admin interface
-------------------------------+--------------------------------------
     Reporter:  ncoghlan@…     |                    Owner:  nobody
         Type:  Uncategorized  |                   Status:  new
    Component:  Uncategorized  |                  Version:  1.3
     Severity:  Normal         |               Resolution:
     Keywords:                 |             Triage Stage:  Unreviewed
    Has patch:  0              |      Needs documentation:  0
  Needs tests:  0              |  Patch needs improvement:  0
Easy pickings:  0              |                    UI/UX:  0
-------------------------------+--------------------------------------
Changes (by kmtracey):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Could you say a bit more about where you looked and found docs lacking?

 This bit: https://docs.djangoproject.com/en/1.3/topics/auth/#writing-an-
 authentication-backend does mention that "The Django admin system is
 tightly coupled to the Django User object described at the beginning of
 this document. For now, the best way to deal with this is to create a
 Django User object for each user that exists for your backend (e.g., in
 your LDAP directory, your external SQL database, etc.)" implying to use
 admin with a custom auth backend you still do want to be using standard
 django.contrib.auth Usesr objects, with all their attributes.

 The descriptions for is_staff, is_active, is_superuser
 
(https://docs.djangoproject.com/en/1.3/topics/auth/#django.contrib.auth.models.User.is_staff)
 all mention how admin uses them.

 https://docs.djangoproject.com/en/1.3/topics/auth/#permissions describes
 how admin uses permissions to control how much access a user has to
 individual models in the admin site.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/17430#comment:1>
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.

Reply via email to