I reported this bug to address cases where merging profiles causes the use to login under a different identity because Launchpad could bot resolve email addresses. Those model changes have landed and this is no longer an issue. User can log in again and they can work. As the reporter of this bug, I and satisfied.
There is a secondary issue where external groups cannot reconcile users with multiple openid identifiers. This users can log in, but secondary services cannot identify the user. This is a feature request, and API changes have been made to accommodate the issue, but it is not clear what other new features are needed to support this use case. ** Changed in: launchpad Importance: Critical => High ** Tags removed: regression ** Tags added: api ** Description changed: - This looks like bug 644824 (reopned?), though may also be bug 676964. - In either case, openid are not matched correctly when the user logins in - through SSO. Since both of these bugs were reported, the - openididentifier table was created to store multiple ids for a user. - Merge may not be dealing with the table correctly. + 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. - There have also been many cases where the email address table (used to - lookup Persons) has a different account from the account in the person - table. This should be an impossibility. Maybe there should be a - constraint, or column should be dropped from person, (or less likely - emailaddress). - - Notes from gmb, 2011-11-24: - - - Dropping account from Person is prohibitively complex (see comments). - - Running the following query: - SELECT COUNT(*) FROM Person, EmailAddress WHERE - EmailAddress.person = Person.id AND - EmailAddress.account <> Person.account; - tells us that there are currently two Persons in the production DB whose Person.account - and EmailAddress.account don't match. - - -- - - From the original question: - One of our guys just recently merged two launchpad acounts into the account nati-ueno. The merge didn't go all the way through - there are times when the old openid gets referenced. - - https://login.launchpad.net/+id/BBze6nw - https://login.launchpad.net/+id/X6dGn6P - - X6dGn6P is the correct one. + 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. -- You received this bug notification because you are a member of Ubuntu Bengali Manual, which is subscribed to LoCo Team Portal. https://bugs.launchpad.net/bugs/881019 Title: Lp login is broken after account merge Status in Canonical SSO provider: Confirmed Status in Launchpad itself: Triaged Status in LoCo Team Portal: Confirmed Status in OpenStack Core Infrastructure: Confirmed Status in Summit - The UDS Scheduler: Confirmed 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. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/881019/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bengali-manual Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-bengali-manual More help : https://help.launchpad.net/ListHelp
