Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No user scopes leads to error
See original GitHub issuefrom @onovotny and copied from https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/issues/241
If you want to use .AddMsal(), there’s no way to do so without any user scopes. It might be needed for Application flows.
If you use new string[0] for the scopes parameter, it’ll throw in the OnAuthorizationCodeReceived callback since options.Scope will be null:
await tokenAcquisition.AddAccountToCacheFromAuthorizationCodeAsync(context, options.Scope).ConfigureAwait(false);
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jennyf19 : proposing to take it in 0.2 given that MSAL.NET fixed it;
Included in 0.1.3-preview release