I am using Django-auth-ldap as my primary authentication backend. Since using this package, I have noticed that our LDAP server (actually, an Active Directory Primary Domain Controller) sometimes cannot be reached by Django (or Outlook, for that matter, but that's a different problem). Django seems to be trying to connect to the LDAP server whenever we are checking the permissions in the view or template currently being accessed by the user that is already logged in.
Now, I do have the standard ModelBackend set up as an alternative if the LDAPBackend authentication fails. Based on what I am reading, though, Django will only change backends during the authentication phase. Am I correct on this? From what I now understand and what seems to be happening, if checking permissions through the LDAPBackend results in an error, Django will raise that error and not move on to the next backend, ModelBackend. Any ideas around this? Thank you so much for your time. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/44ad1bced94b4322b20fa2524559e013%40ISS1.ISS.LOCAL. For more options, visit https://groups.google.com/d/optout.
