On Jan 29, 5:15 am, Waldemar Kornewald <[email protected]> wrote: > What exactly was the problem? Could you please post the settings > backend code here?
This is what I was following: http://docs.djangoproject.com/en/dev/topics/auth/#writing-an-authentication-backend > Did you try to add a few logging.info() calls into your backend in > order to verify that the code gets executed, at all, and in order to > check which line fails? I had more logging calls than non-logging calls. I'm not sure what the problem was, but my code seemed to stop executing (I think when I tried to construct the User()) without even raising anything. Hence my unsuccessful attempted foray into pdb-land. I can only guess Python was getting mixed up with namespaces or something, but that's a guess. I finally just created my own User class. > > 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. > > It's probably better to have a proxy user in the DB or at least fake a > user entry (not saved in DB) with a faked key_name, so other code can > store ReferenceProperties to that fake user. This is what everybody keeps telling me... I'm not familiar with Django yet. What is the "other code" that needs to reference DB users? I'm trying to build a super-light non-DB app, but if I have to create Users in DB I will. I just don't know why yet. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
