Hi Scott, I came back to your LDAPSupport. The pre_auth_bind is a little bit tricky evan with mk_pre_auth_bind, but I got it (after a while :)
And there seems a problem with pre_auth_bind() and update_user(): You let construct somebody a pre_auth_bind() which search for the dn of a user, but on the other side you construct in update_user() always your own search. If pre_auth_bind() returns a valid user-dn, this would be the same dn for updating the user object. I would asume that update_user() call the ldap-object by the dn directly (if a user-object as a dn-attribute, which needs to be stored!) or if the user-object is new the update_user() should use the same search which is done in the custom pre_auth_bind(). Regards, Dirk -- "Feel free" – 10 GB Mailbox, 100 FreeSMS/Monat ... Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
