Launchpad itself

Problem with merged account and OpenID

Asked by Julien Danjou

Due to bug 881019, when I log into Launchpad the wrong OpenID is being
passed to third party systems. The OpenID that is listed on my
Launchpad home page is:
https://login.launchpad.net/+id/zwY3xB7

However the one that is being passed when I authenticate is:

https://login.launchpad.net/+id/WxpdwPD

Would you please delete that OpenID so that only the one correctly
listed on my home page is passed?

Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Last query:
Last reply:
Revision history for this message
David Ames (thedac) said : 		#1

Julien,

I have deleted the extra openid:

https://login.launchpad.net/+id/WxpdwPD

--
David Ames

Revision history for this message
James E. Blair (corvus) said : 		#2

When he logs into OpenStack's Gerrit with his launchpad ID, https://login.launchpad.net/+id/WxpdwPD is still the ID that's being passed.

Revision history for this message
William Grant (wgrant) said : 		#3

Webops: please delete all OpenIDIdentifiers for the Launchpad account. WxpdwPD will be the one that survives, as it's the true identity of the SSO account.

Julien will then need to log into Launchpad to teach it which one is right, and then wait for gerrit's cronjob to update their DB.

Revision history for this message
David Ames (thedac) said : 		#5

Julien, I have discussed this with a few people. Right now the zwY3xB7 does not appear in the DB but WxpdwPD does. Can you please log out completely and maybe even clear your browsers cache and then log back in? We'll take more drastic measures if this does not resolve the problem.

Revision history for this message
Julien Danjou (jdanjou) said : 		#6

I can try that but since the zwY3xB7 has been added to the third party system I use manually, I'm not able to see which OpenID is being passed anyway. If you know some way to debug this, I could try things.

Revision history for this message
William Grant (wgrant) said : 		#7

We know this fixes the problem, so as long as it works for you it's fine.

Can you help with this problem?

Provide an answer of your own, or ask Julien Danjou for more information if necessary.

To post a message you must log in.