Gerrit account linking. |
||||||
Issue descriptionHi everybody. I am trying to follow the instructions at http://www.chromium.org/chromium-os/developer-guide/gerrit-guide under "(Googler) Link @chromium.org & @google.com accounts" and what happens is that when I receive the verification email and visit the page, I get the error "Identity in use by another account". I am not sure, then, whether the two accounts are already linked or not and if that is the case why I cannot see it from the Identity page in the settings. Thanks! Cheers, Armando
,
Apr 6 2017
No idea what that error message is. I manually linked your accounts, and things look normal to me from here. Can you check if everything is working as expected?
,
Apr 6 2017
Could it be possible that, because the accounts were already linked the webapp is simply lamenting that this is already done? Also, what is the best way to verify that this is in fact the case, namely that the two accounts are linked? Thanks! Armando
,
Apr 10 2017
,
Apr 10 2017
You can check by examining your account's identities: https://chromium-review.googlesource.com/#/settings/web-identities (If you have PolyGerrit enabled, you will need to disable it for this, as a PolyGerrit identity view doesn't exist ATM.) Your theory seems plausible; however, I'm not too familiar with the Gerrit linking internals. If you'd like to dive deeper, I suggest that you contact the GoB team: http://go/gob-ticket
,
Apr 10 2017
,
Apr 10 2017
Ok, disabling the PolyGerrit indeed shows both accounts listed in identities when looking at the page using the @google.com account. When I try to access the page using the @chromium.org account I get an error message that says "armax@chromium.org has already been registered under a different account" which at this point I assume is WAI? If that's the case the bug can be closed.
,
Apr 10 2017
,
Apr 10 2017
If it shows the accounts as linked, then this bug is fixed. If you have any issues using services, please file a new separate bug. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by estaab@chromium.org
, Apr 5 2017