On May 11, 7:50 am, Ivan Sagalaev <[EMAIL PROTECTED]> wrote: > > At the moment, django.contrib.auth does not support creating a user > > account without setting a password. > > Why not generate a random one? It won't break an ability to authenticate > using OpenID or any other backend for that matter. I've used this > approach with my OpenID auth backend and didn't encounter any downsides.
The problem with using a random password is that you can't answer the question "does this account have a password set?". I need to be able to answer that question because my OpenID implementation allows users to associate mupltiple OpenIDs with a single account. I want to let them delete associations as well, but prevent them from deleting the very last association unless they have set a password for their account (to stop them from locking themselves out). --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
