On Thursday, June 16, 2011 2:38:52 PM UTC+2, SleepyCal wrote: > > > Having a central authorization point is the way forward. I'm a bit confused > by this comment though: > > "But this still do not solve problem of NOT having multiple accounts in > several django projects" > > Could you explain what you mean? >
As far as I know, using authorization like Google Account, Facebook or OpenID just makes that user has an auto generated account in Django connected with external account (for example Google Account). So still - you bypass only the fact of logging, but storing/editing user profile, some other additional data is complicated and involves using this auto-generated accounts in django. I hope you get my point. -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/8qBkZkMn5E0J. 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.
