You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// Used by Web APIs, which cannot interact with the user, when they run into a situation where user consent is required for additional scopes.
452
-
/// This method appends in the HttpResponse being sent back to the client, a 403 (forbidden) status code and populates the 'WWW-Authenticate' header with additional information.
453
-
/// The client, when it receives the 403 code with this header, can use the additional information provided in the header to trigger an interaction with the user where the user
454
-
/// can then consent to additional scopes.
451
+
/// Used in Web APIs (which therefore cannot have an interaction with the user).
452
+
/// Replies to the client through the HttpReponse by sending a 403 (forbidden) and populating wwwAuthenticateHeaders so that
453
+
/// the client can trigger an iteraction with the user so that the user consents to more scopes
455
454
/// </summary>
456
-
/// <param name="scopes">The additional scopes that the user needs to consent to</param>
457
-
/// <param name="msalServiceException"><see cref="MsalUiRequiredException"/> The MsalUiRequiredException that is examined to see if there is case for this response.</param>
458
-
455
+
/// <param name="scopes">Scopes to consent to</param>
456
+
/// <param name="msalServiceException"><see cref="MsalUiRequiredException"/> triggering the challenge</param>
// A user interaction is required, but we are in a Web API, and therefore, we need to report back to the client through an wwww-Authenticate header https://tools.ietf.org/html/rfc6750#section-3.1
0 commit comments