OK, I was confused about why Django still needs usernames in its database even though LDAP is the new authentication method. I thought it would require authenticating via LDAP, then checking for the user _and_ pass in Django's database. I didn't realize that I will only have to copy the username (not the password), and that authentication does not need to occur a second time against the Django user list. It looks like I'll be able to convince the man in charge that Django is a great framework choice for our needs.
Thanks to all for the feedback! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
