We (=Canonical IS) have had a few tickets filed for this problem on summit.ubuntu.com as well.
In each case when I look at the user's accounts, there is a Django user "foo" and a user "foo2". User "foo" has no password set and no matching row in django_openid_auth_useropenid, but user "foo2" does have such a row and also no password set. Switching the usernames of the Django accounts around fixes (or "fixes" ... but so far so good) the symptoms for that particular user. -- You received this bug notification because you are a member of loco- directory-dev, which is the registrant for loco-directory. https://bugs.launchpad.net/bugs/639772 Title: New user name after LP login Status in OpenID integration for django.contrib.auth: Confirmed Status in LoCo Directory: Fix Released Status in Summit: Confirmed Bug description: Today I wanted to register for an event on the loco.ubuntu.com web site which required me to login to LaunchPad. My user name is "netritious" but for some reason loco.ubuntu.com thinks I am "netritious2". _______________________________________________ Mailing list: https://launchpad.net/~loco-directory-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~loco-directory-dev More help : https://help.launchpad.net/ListHelp
