#3669: Restructure django.contrib.auth, make Models replaceable
---------------------------------------------------------+------------------
   Reporter:  David Danier <[EMAIL PROTECTED]>  |                Owner:  adrian 
     
     Status:  closed                                     |            
Component:  Contrib apps
    Version:  SVN                                        |           
Resolution:  duplicate   
   Keywords:  auth rewrite replace models                |                
Stage:  Unreviewed  
  Has_patch:  0                                          |           
Needs_docs:  0           
Needs_tests:  0                                          |   
Needs_better_patch:  0           
---------------------------------------------------------+------------------
Comment (by David Danier <[EMAIL PROTECTED]>):

 Replying to [comment:3 Gary Wilson <[EMAIL PROTECTED]>]:
 > Perhaps you were looking for #3011?
 
 Not really, this ticket does things very different. I merged my approach
 with ideas of the the generic-auth-branch, as I think this goes side-by-
 side. Additionaly I separated things up to get django more flexible (users
 and permissions are two different apps, user-backends is a possible addon-
 app). With this changes it is easy to replace the current models
 (including the groups and message-system, as not everyone uses this...this
 could be put into separate apps, too) or implement things like row-level-
 permissions very easily. However some generic API stays that can be used
 by third-party-apps to ensure usage of one user-system (needed for single-
 sign-on solutions or simply to ensure the usage of only one user-table).
 Usersystems that are using some non-db backend are also possible, but may
 need to provide some model to get foreign keys working (current solution
 needs you to copy the user to the django-model and return this...usage of
 LDAP is very ugly with this approach).
 
 As I updated to branch under https://svn.webmasterpro.de/django-auth-
 rewrite/ things may get more clearly:
  * https://svn.webmasterpro.de/django-auth-rewrite/django/contrib/auth/ -
 generic API to be used by apps
  * https://svn.webmasterpro.de/django-auth-
 rewrite/django/contrib/auth_backends/ - ideas for some backends-system
 (not really needed, but to retain current functionality...only some idea
 so far)
  * https://svn.webmasterpro.de/django-auth-
 rewrite/django/contrib/auth_user/ - user-system including groups and
 messages (copy of current solution)
  * https://svn.webmasterpro.de/django-auth-
 rewrite/django/contrib/auth_model_perm/ - model permissions (copy of
 current solution)
 
 Note: The code is still only some proof-of-concept. The generic API works
 here, but as I replaced the user- and permission-system I haven't really
 tested this. In addition many things inside django need to be arranged
 (generic views for example).
 
 I'll leave this ticket closed, but comments are always welcome.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3669#comment:4>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to