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
It's not clear how to pass specific messaging from the authorization handlers, which has the context on why a request was forbidden, to the authentication's scheme handlers, which formats the response to users when context.Fail has been called.
It looks like something in httpContext.Authentication could provide a way to pass messaging back to the scheme handler (IAuthenticationHandler) but this appears to be a deprecated property and so clarification would be useful.
The rest of the article is detailed and great, I think this final step is missing that would help complete the article
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: b1141d92-adeb-6841-229f-914c808f9a2b
Version Independent ID: 7089b376-949f-c1c6-c37a-5d8cc7ecf104
It's not clear how to pass specific messaging from the authorization handlers, which has the context on why a request was forbidden, to the authentication's scheme handlers, which formats the response to users when context.Fail has been called.
It looks like something in httpContext.Authentication could provide a way to pass messaging back to the scheme handler (
IAuthenticationHandler
) but this appears to be a deprecated property and so clarification would be useful.The rest of the article is detailed and great, I think this final step is missing that would help complete the article
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: