I have the same issue, but my issue is that Django is interfacing with a web service and ideally will have *no user database* on the front end. All the examples I've seen involve essentially copying the user from LDAP/wherever and sticking them in the User model, which:
a) Is duplication across services (which creates lots of uninteresting and painful synchronisation problems); and b) Doesn't solve my problem at all. Is it stupidly difficult to do what I wanted to do? If I create my own AnonymousUser etc. objects and write an auth-backend to use in AUTHENTICATION_BACKENDS, will I be able to make it work? It all seems really tightly coupled to the User model at the moment. PS: I Googled loads, and came up with *only* examples using the User model. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
