Correct Behaviour for Requesting Incorrect Scopes

Viewed 31

In regard to OpenID Connect and the MSAL library, what should the correct behaviour be if you request incorrect scopes, i.e. incorrectly spelt, or non-existent scopes?

We're testing this with Azure AD B2C and a React website using MSAL and when we try to acquire the token we simply get an empty result. Is this the correct behaviour or should we get an error?

0 Answers
Related