django_openid_auth/auth.py line 71 checks the claimed id against
existing ones in Django mapping user to openid account. The only thing
I can figure is that we already had a user and openid mapping for him,
but on this login we were given a different openid claimed id for the
user than what we already had stored.
Consequently, it treated him as a new user, and since there was already
a "netritious" django.auth.models.User account with that username, on
line 104 is started adding an incrementing number to the username. This
means there's likely also a "netritious1" user account and openid
mapping, meaning this has happened at least twice now.
** Also affects: django-openid-auth
Importance: Undecided
Status: New
--
New user name after LP login
https://bugs.launchpad.net/bugs/639772
You received this bug notification because you are a member of loco-
directory-dev, which is the registrant for loco-directory.
Status in OpenID integration for django.contrib.auth: New
Status in LoCo Directory: New
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
