Harmonise Microsoft Authentication APIs with AAD "v2" and MSAL concepts #277
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.
Refactor the
MicrosoftAuthentication
component API signature to accept a set of scopes (string[] scopes
) rather than a single "resource ID", and drop the no-longer used remote URL parameter.Introduce a new wrapper type for the authentication result such that we can drop the dependency on the JWT library and not expose the MSAL
AuthenticationResult
type either. We only need the access token (as a string) and the account UPN.Note that technically before we should not have been trying to parse the access token as a JWT because there is no guarantee that STS returns JWTs - they should be treated transparently.