Lp login is broken after account merge
Bug #881019 reported by
Curtis Hovey
This bug affects 39 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical SSO provider |
Confirmed
|
High
|
Unassigned | ||
Launchpad itself |
Triaged
|
High
|
Unassigned | ||
LoCo Team Portal |
Confirmed
|
Critical
|
Unassigned | ||
Summit |
Confirmed
|
Critical
|
Unassigned |
Bug Description
After users merge Launchpad profiles, they will have multiple OpenId Identifiers from Ubuntu's Single Signon Service. Users might be blocked from using external services because those services are not aware of, or cannot manage multiple identifies per user.
This bug originally described an issue where Launchpad user profiles were associated with a different set of addresses from their accounts. The fix was to never associate email addresses with accounts so that Launchpad is not confused about who the person is.
Changed in launchpad: | |
status: | New → Triaged |
importance: | Undecided → Critical |
tags: | added: merge-deactivate openid regression users |
Changed in launchpad: | |
assignee: | nobody → Graham Binns (gmb) |
Changed in launchpad: | |
status: | Triaged → In Progress |
Changed in launchpad: | |
assignee: | Graham Binns (gmb) → nobody |
Changed in summit: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in openstack-ci: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in loco-team-portal: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in canonical-identity-provider: | |
status: | New → Confirmed |
importance: | Undecided → High |
no longer affects: | openstack-ci |
Changed in canonical-identity-provider: | |
status: | Confirmed → In Progress |
Changed in launchpad: | |
status: | Triaged → Fix Released |
Changed in loco-team-portal: | |
status: | Confirmed → Fix Released |
Changed in summit: | |
status: | Confirmed → Fix Released |
Changed in canonical-identity-provider: | |
status: | In Progress → Confirmed |
Changed in launchpad: | |
status: | Fix Released → Triaged |
Changed in loco-team-portal: | |
status: | Fix Released → Confirmed |
Changed in summit: | |
status: | Fix Released → Confirmed |
To post a comment you must log in.
About dropping columns. It would seem at first glance that the person column should be dropped from emailaddress to ensure that person are looked up via account. This breaks team and unactivated profiles which do not have accounts. It is possible to drop account from person...it is rarely used and can be gotten via the email address or query against account.
The other option is to drip account from email address so the table is restored to the schema before the SSO mess.