exactly, thanx english isn't my first language, sorry.
Perhaps we'll have group and user ldap storage? :) On 5/16/06, gabor <[EMAIL PROTECTED]> wrote: > > Joseph Kocherhans wrote: > > On 5/16/06, Douglas Campos <[EMAIL PROTECTED]> wrote: > >> the multi-auth branch targets some kind of 100% external auth? because > >> i've seen some approach using ldap+django users > > > > I'm not sure what you mean by "100% external" but the backends that > > get used are controlled by the AUTHENTICATION_BACKENDS settings > > variable. This is a tuple of python paths, so you can do something > > like this: > > > > AUTHENTICATION_BACKENDS = ( > > 'django.contrib.auth.backends.ModelBackend', # for django users > > 'myapp.LDAPBackend', # write your own LDAP backend > > ) > > i think what he meant are things like the admin-system. > will it be possible to for example: > > - authenticate with let's say LDAP > - use the admin system > - never create any django.contrib.auth.models.User objects > > ? > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
