New user name after LP login
Bug #639772 reported by
R G
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
LoCo Team Portal |
Fix Released
|
High
|
Michael Hall | ||
Summit |
Fix Released
|
High
|
Michael Hall | ||
django-openid-auth |
Fix Released
|
Undecided
|
Unassigned |
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".
Related branches
lp:~mhall119/django-openid-auth/strict-username-requirements
- James Henstridge: Approve
- Anthony Lenton: Approve
-
Diff: 147 lines (+82/-2)3 files modifiedREADME.txt (+10/-0)
django_openid_auth/auth.py (+13/-2)
django_openid_auth/tests/test_views.py (+59/-0)
lp:~mhall119/loco-team-portal/fixes-639772
- LoCo Team Portal Developers: Pending requested
-
Diff: 99 lines (+55/-3)4 files modifiedloco_directory/common/launchpad.py (+34/-0)
loco_directory/teams/management/commands/lpupdate.py (+6/-3)
loco_directory/teams/management/commands/update-openids.py (+13/-0)
loco_directory/userprofiles/models.py (+2/-0)
lp:~cjohnston/loco-team-portal/openid
- Michael Hall (community): Approve
-
Diff: 248 lines (+92/-16)5 files modifiedloco_directory/common/views.py (+28/-2)
loco_directory/locale/loco-directory.pot (+11/-13)
loco_directory/settings.py (+3/-0)
loco_directory/templates/login_failure.html (+40/-0)
loco_directory/urls.py (+10/-1)
lp:~cjohnston/summit/openid
- Michael Hall (community): Approve
-
Diff: 13 lines (+3/-0)1 file modifiedsummit/settings.py (+3/-0)
Changed in loco-directory: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in loco-directory: | |
status: | Confirmed → In Progress |
assignee: | nobody → Michael Hall (mhall119) |
milestone: | none → 0.2.22 |
status: | In Progress → Fix Committed |
Changed in loco-directory: | |
milestone: | 0.2.22 → 0.3.0 |
Changed in loco-directory: | |
status: | Fix Committed → Fix Released |
Changed in django-openid-auth: | |
status: | New → Confirmed |
Changed in summit: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in django-openid-auth: | |
status: | Confirmed → Fix Committed |
Changed in summit: | |
status: | Confirmed → In Progress |
Changed in summit: | |
status: | In Progress → Fix Released |
assignee: | nobody → Michael Hall (mhall119) |
Changed in django-openid-auth: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.