Hi, I had a look at the LDAP Auth Backend. [1]
It works for authentication, but groups are not supported yet. The user information gets copied from LDAP to the database. You could use the same method for groups, too. But when should changes in LDAP be copied to the django database? 1. If a user logs in. 2. A standalone application syncing every N minutes. At first I was disappointed, because the data gets copied. It's redundant and that's something I like to avoid. But if the user or group model is used as a foreign key somewhere (e.g. session). you must have the user in the database. One way around it, would be to use strings instead of foreign keys.... But mainting a copy of the session module is no fun. Permission checking would have to be implemented, too. Does anyone know these problems? How did you solve them? Thomas [1] http://code.djangoproject.com/ticket/2507 -- Thomas Guettler, http://www.thomas-guettler.de/ E-Mail: guettli (*) thomas-guettler + de --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
