Files
gerrit/devutil
Shawn O. Pearce dd8543d03d Automatically upgrade legacy Gerrit 1 accounts to Gerrit 2 on first login
If the OpenId provider was the Google Account provider and the user
already exists with an external id of "GoogleAccount/$email" then
they were imported off a Gerrit 1 schema and we can trust that the
identity is still the same individual.

We also now support more than one OpenId string per account; this
may be necessary to allow users who have more than one OpenId to
link all of their accounts together within Gerrit.  Currently we
do not have a way for users to manage this linkage on their own,
but we might support it in the future by emailing tokens or some
other sort of method.

Keeping the legacy 'GoogleAccount/$email' identity really helps
during testing, as Google's OpenID provider creates different key
strings for each hostname:port combination it sees for an account.

By allowing multiple external strings and keeping our special legacy
entry we can permit developers to bind back to their own accounts
no matter how they started the development server, or no matter
what URL they used to access it.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-12-02 13:00:59 -08:00
..