I spent much of the day trying to diagnose this problem with Charlie and Anthony. In the previous comment, Anthony describes what we agreed should be the long term solution, barring objections from Stuart; and what we all thought ought to work as the short term solution.
To be clear, this appears to have been a failure of the LP Foundations team/myself in identifying our change (which allows multiple openids to be associated with a single LP account, thereby fixing several bugs) as a potential problem that needed to be presented to ISD and tested. We believed it would be transparent, and it was not. We will learn from this.
Charlie was very accommodating in trying different variations of our short term solutions. He did each one with a new browser profile, so browser cookies, such as on directory.c.c, should not have been an issue. He tried logging out of Launchpad and SSO. None of it worked. We still do not have a workaround. This needs to be worked on until we have a workaround--he and Ali have access.
The original bug description says that the user created a second LP account. AFAICT, while checking with Charlie confirmed that this was his perception, from a technical perspective, this really means that he clicked on Login/Register, *which took him to the SSO application*. Therefore, I'm pretty sure that's what happened.
I tried duplicating the problem with a new email address on my own account. I was unable to, and various hypotheses I had were dead ends.
I'll pass this on to stub for more work on a workaround. His familiarity with the DB will hopefully resolve this in short order.
I spent much of the day trying to diagnose this problem with Charlie and Anthony. In the previous comment, Anthony describes what we agreed should be the long term solution, barring objections from Stuart; and what we all thought ought to work as the short term solution.
To be clear, this appears to have been a failure of the LP Foundations team/myself in identifying our change (which allows multiple openids to be associated with a single LP account, thereby fixing several bugs) as a potential problem that needed to be presented to ISD and tested. We believed it would be transparent, and it was not. We will learn from this.
Charlie was very accommodating in trying different variations of our short term solutions. He did each one with a new browser profile, so browser cookies, such as on directory.c.c, should not have been an issue. He tried logging out of Launchpad and SSO. None of it worked. We still do not have a workaround. This needs to be worked on until we have a workaround--he and Ali have access.
The original bug description says that the user created a second LP account. AFAICT, while checking with Charlie confirmed that this was his perception, from a technical perspective, this really means that he clicked on Login/Register, *which took him to the SSO application*. Therefore, I'm pretty sure that's what happened.
I tried duplicating the problem with a new email address on my own account. I was unable to, and various hypotheses I had were dead ends.
I'll pass this on to stub for more work on a workaround. His familiarity with the DB will hopefully resolve this in short order.