mumble username problem

This issue sounds like the email address used to login was once associated with a merged acount. That account still hase and openid field so it is used instead of the master account.

I have seen something like this happen on Launchpad once. We decided to mutate the merged account's openid to prevent it from being used. There is a script in the launchpad tree that can fix historic accounts. maybe it can be adapted to SSO.

    database/schema/pending/update-merged-person-accounts.sql

We currently obtain the username from a table replicated from launchpad's database and the matching is also done on a similar table so I'm not sure that we can do anything to fix this in the SSO DB itself.

So this is a bug in the launchpad database? Do I need to log a bug somewhere else?

No. I've contacted the launchpad guys and they'll re-claim this question once they've confirmed it's something which needs fixing on their side.

If the user name is wrong, that implies my orginal assumption that the user has two openids is correct. The script I suggested above database/schema/pending/update-merged-person-accounts.sql may fix this issue.

Is there a bug open on this? person_merge needs to cope or the SSO needs to detect the merge form the lp_person record

Curtis' script looks fine and I hae fixed the current data

Yes bug 575317, The code is fixed on edge. The script fixes the historic data to work with the account split.

So this problem is fixed on edge, but not the main launchpad database yet?

I just tried running mumble again and it still has the same problem. I did run
mumble from the command line and noticed in the start-up messages it says
this about my "UserState":

UserState:
session: 521
name: "Matt Waddel (markskilbeck-deactivatedaccount)"
user_id: 1000000113
channel_id: 18
comment: "mattman"

Hm. Edge uses the main Launchpad database, so no, that's not the problem.

Perhaps it needs to be replicated still to the SSO DB? I'll pass this to Stuart Metcalfe in the hopes that he might know.

It's possible that the mumble plugin is caching the original username - I'd need to get someone to take a look at how the code handles subsequent logins. I'm afraid that's unlikely to happen this week.

On Tue, 2010-05-25 at 15:10 +0000, Matt Waddel wrote:
> Question #111745 on Launchpad Foundations changed:
> https://answers.edge.launchpad.net/launchpad-foundations/+question/111745
>
> Status: Answered => Open
>
> Matt Waddel is still having a problem:
> So this problem is fixed on edge, but not the main launchpad database
> yet?

Edge is the main database.

> I just tried running mumble again and it still has the same problem. I did run
> mumble from the command line and noticed in the start-up messages it says
> this about my "UserState":

--
__Curtis C. Hovey_________
http://launchpad.net/

Another new employee, that started about the same time I did, has
this same problem. His username shows up as a string of random
characters, that almost look like an automatically generated password.

That sounds like the generated unique identifier which would be returned if no matching launchpad username is found. Please provide details of the other new employee (launchpad username, ideally) so we can investigate both cases. Thanks

His name is John Rigby. His name shows up as John Rigby (zpXbypE)

This problem still exists with my account. Kiko pointed out
this morning that there actually is a launchpad account
called "markskilbeck-deactivatedaccount". Any ideas how
this is bleeding over into my username?

https://launchpad.net/~markskilbeck-deactivatedaccount

Should this be logged as an official bug? It seems to be
affecting all new starters. Kate Stewart is seeing this
problem - https://launchpad.net/~kate.stewart

Yes, this should be logged as an official bug and given a high priority.

https://bugs.launchpad.net/canonical-identity-provider/+bug/688660

Update -There has been a fix posted for this defect, it should be tested and released with the next SSO cycle.

This problem is fixed now. Thanks.