Page MenuHomePhabricator

Read both older "key" and newer "accountId" identifiers from JIRA during authentication

Authored by epriestley on Feb 23 2020, 1:36 AM.
Referenced Files
Unknown Object (File)
Thu, Apr 18, 4:33 AM
Unknown Object (File)
Sat, Apr 6, 9:35 PM
Unknown Object (File)
Sun, Mar 31, 5:43 AM
Unknown Object (File)
Mar 14 2024, 6:07 PM
Unknown Object (File)
Feb 3 2024, 11:45 PM
Unknown Object (File)
Feb 1 2024, 8:53 PM
Unknown Object (File)
Jan 25 2024, 2:15 AM
Unknown Object (File)
Jan 11 2024, 12:05 PM



Depends on D21022. Ref T13493. The JIRA API has changed from using "key" to identify users to using "accountId".

By reading both identifiers, this linkage "just works" if you run against an old version of JIRA, a new version of JIRA, or an intermediate version of JIRA.

It also "just works" if you run old JIRA, upgrade to intermediate JIRA, everyone refreshes their link at least once, then you upgrade to new JIRA.

This is a subset of cases and does not include "sudden upgrade to new JIRA", but it's strictly better than the old behavior for all cases it covers.

Test Plan

Linked, unlinked, and logged in with JIRA. Looked at the "ExternalAccountIdentifier" table and saw a sensible value.

Diff Detail

rP Phabricator
Lint Not Applicable
Tests Not Applicable