I think the problem was that the Django "User" and ragendja "User" were conflicting somehow and causing strange problems with the runtime.
For my custom backend I'm now creating my own "User" and ignoring both of those (neither of which I could get to work properly). My Users don't persist in the DB (auth is done remotely), and I have been warned this may cause problems for the admin site due to messaging issues, but we don't use the admin site anyway. I'm sure it will cause other problems too. We shall see. On Jan 27, 3:27 pm, boson <[email protected]> wrote: > I'm trying to write a custom authentication backend for Django, as > described here: > > http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-authenti... > > I started with the simple "SettingsBackend" example in the docs, and > that doesn't even work. As soon as I try to construct a User object, > it's like the code just stops running. Nothing after this gets run, > and no exception is raised. Yet the login page renders properly and > says "Invalid Login". > > I'm totally stumped, and don't even understand how this is possible. > Any suggestions? > > P.S. Haven't even tried in the cloud yet. This is just with local > runserver. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
