Without knowing what is in the loco.ubuntu.com app's database, it is a
bit hard to know what the problem is. What Michael describes is how the
"netritious2" user name would have appeared.
If you've got access to that database, running the following query
should help determine what is going on:
SELECT auth_user.username, django_openid_auth_useropenid.claimed_id
FROM auth_user LEFT JOIN django_openid_auth_useropenid
ON (auth_user.id = django_openid_auth_useropenid.user_id)
WHERE auth_user.username LIKE 'netritious%';
There are two possibilities here: (a) there was an account called
"netritious" in the database prior to using django_openid_auth with no
OpenID identifier associated, or (b) someone else authenticated via
OpenID and provided the "netritious" as a nickname first.
--
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
