Canonical SSO provider

Please help annegentle with openid log in issue

Asked by Gary Poster

Hi.

as reported by mtaylor on #launchpad-dev:
"""one of our devs (~annegentle) has launchpad openid returning a different localid than annegentle. apparently this happened with adamg a little while ago and the working hypothesis is that it is related to having had an account get renamed"""

additional info from jeblair:
"""https://launchpad.net/~annegentle says the local_id is https://login.launchpad.net/+id/6sDWhGL
but when she logs in, we get passed https://login.launchpad.net/+id/xQHRTxt
and she did say that she has had some kind of account rename (i don't know if it was executed as a merge)"""

I think this is another instance of https://bugs.launchpad.net/canonical-identity-provider/+bug/644824 which you all dealt with before in https://answers.launchpad.net/canonical-identity-provider/+question/150135 . I have asked LOSAs to clear out the openids in Launchpad so as long as the user does not try to use the two openids again, she should be OK. However, I think it would be good to delete the unwanted one on the CIP side as well.

Thank you

Gary

Question information

Language:
English Edit question
Status:
Solved
For:
Canonical SSO provider Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Selene ToyKeeper (toykeeper) said : 		#1

Could you be a little more clear about what the symptoms of the problem are, and what action is requested? Which account is unwanted, and what are the email addresses associated with both accounts? Should the SSO accounts be merged? Should one SSO account be deleted?

One of the questions here probably describes the process for getting this fixed: https://wiki.ubuntu.com/SSO/FAQs

Revision history for this message
Gary Poster (gary) said : 		#2

Hi. Thank you for the reply.

AIUI, the symptom was as described here, as well as in the question and bug to which I linked. That said, the problem report was second-hand, and is now third-hand for you.

The user did something, probably trying to change her login by adding an SSO account, which then triggered the divided-account issue in bug 644824. The FAQs you mentioned look good, but she was unaware of them.

A reasonable short-term solution was to clear out the openids in Launchpad, per the bug comments. We did this, and AFAIK, that worked.

It looks like you described a better short-term and medium-term solution in question 150135. It's better because it removes the possibility of a land mine in the future, if the user mistakenly logs in with the wrong account in the future. That's what I was requesting in this question. Am I right that a merge would be the safest variation of this solution for her, given that we do not have first-hand knowledge of what she actually wants, and that she probably doesn't care except that her Launchpad login continues to work?

A longer-term solution for other users who go down this road would be to close the bug, of course, but I don't know/remember if that would help users retroactively.

Thanks again,

Gary

Revision history for this message
Selene ToyKeeper (toykeeper) said : 		#3

I asked annegentle about this on IRC and she says she is no longer experiencing any issues. If she experiences any further difficulties, feel free to re-open this.