OAuth 2.0 against a Data Center instance's own provider.
A separate strategy from oauth2 rather than a flag on it, because the two differ in what they talk to. Cloud 3LO
tokens are minted by auth.atlassian.com and accepted only through the Atlassian gateway, so host is derived from
a cloud id; a Data Center instance is its own authorization server and its own API host, so host is required and
is the only address involved. Folding them together would mean one strategy where host is both forbidden and
mandatory.
redirectUri sits with the refresh credentials because the Data Center provider validates it on the refresh grant,
not only on the initial exchange.
OAuth 2.0 against a Data Center instance's own provider.
A separate strategy from
oauth2rather than a flag on it, because the two differ in what they talk to. Cloud 3LO tokens are minted byauth.atlassian.comand accepted only through the Atlassian gateway, sohostis derived from a cloud id; a Data Center instance is its own authorization server and its own API host, sohostis required and is the only address involved. Folding them together would mean one strategy wherehostis both forbidden and mandatory.redirectUrisits with the refresh credentials because the Data Center provider validates it on the refresh grant, not only on the initial exchange.