Use access_token grant instead of refresh_token #2153
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This substantially mitigates #1959 or possibly eliminates the issue entirely. Changing the ADAL token <=> ACR token exchange's
grant_type
toaccess_token
, and not passing in the ADALrefresh_token
, dramatically reduces the size of the obtained ACRrefresh_token
. My token's size was pretty consistently about 950 bytes, compared to > 2600 before.It may be functionally impossible to get a token using this different mechanism that is too long for Docker CLI. We won't update people's existing Docker configs (at least not now...), but we hopefully will never need to suggest disabling Wincred again.
The disadvantage to this grant type is that if the ADAL
access_token
is near expiry, they (ACR) will not be able to use the ADALrefresh_token
to get a new one--however, that shouldn't be an issue for us since we get a fresh ADAL token from the Azure Account extension every time.