"tonemcd" <[EMAIL PROTECTED]> writes: > You do mention that every entry in LDAP must also exist in the django > users table as well - is that a fundamental requirement?
I've written very similar django-to-ldap glue code to this, and what I did was treat the django User model as a cache of data in ldap. I have a login view that, if a matching django user cannot be found, but ldap authentication succeeds, creates the django user, then imports information about them into the User object from ldap and saves the user. The user object could be deleted on logout, or periodically by a grim record reaper but I haven't found that necessary yet. -- +----------------------------------------------------------------+ | Jason F. McBrayer [EMAIL PROTECTED] | | "If you wish to make Pythocles wealthy, don't give him more | | money; rather, reduce his desires." -- Epicurus |
