#3011: Allow for extendable auth_user module
------------------------------------+---------------------------------------
          Reporter:  nowell strite  |         Owner:  seocam   
            Status:  assigned       |     Milestone:           
         Component:  Contrib apps   |       Version:           
        Resolution:                 |      Keywords:  auth_user
             Stage:  Accepted       |     Has_patch:  1        
        Needs_docs:  1              |   Needs_tests:  1        
Needs_better_patch:  1              |  
------------------------------------+---------------------------------------
Comment (by David Danier <[email protected]>):

 Replying to [comment:56 seocam]:
 > Replying to [comment:55 seocam]:
 > > Even if this patch it's not what we are looking for I'd like to the
 this ticket.
 > to get this ticket*

 I like to have some fix for this in Django, too....but I see one major
 downside on the approach of patching everything together to support these
 things: If you look at my proposal above you may agree, that - for example
 - having AUTH_BACKENDS is not neccessary to support different backends.
 One could just implement some kind of LdapUser-Model (which only has
 fields, that are really needed for LDAP) and use this. You can say similar
 things about AUTH_PROFILE_MODULE, which would be not neccessary any more.

 So perhaps instead of creating an continuous growing contrib.auth-module
 it would be a good idea to concentrate on replacing it by something that
 reduces the overall overhead (in code and management). For me it looks
 like currently many things get patched in whithout getting down to the
 real problems and by providing many half-ready solutions on the road down
 to a flexible authentication system.

 Why half-ready? AUTH_PROFILE_MODULE is a good example here. You may use
 user.get_profile() to load the profile for a particular user. But there is
 no way to auto-create the profile for new users (like get_or_create()). So
 you have to write your own register-view to get this working, or use some
 other way to work around this (I think there is some closed ticket for
 this, too).

-- 
Ticket URL: <http://code.djangoproject.com/ticket/3011#comment:57>
Django <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