AuthorizationFilterContext no longer relevant in .NET Core 3.0

[IGx89]

The last section in these docs talks about using AuthorizationFilterContext in HandleRequirementAsync, but context.Resource doesn't appear to be AuthorizationFilterContext anymore in .NET Core 3. See dotnet/aspnetcore#11075. I would love to see updated documentation for .NET Core 3 showing specifically how to access RouteData -- currently migrating a 2.2 webapp to 3.0 and that's one of the issues that came up.

---

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
• Content: Policy-based authorization in ASP.NET Core
• Content Source: aspnetcore/security/authorization/policies.md
• Product: aspnet-core
• Technology: aspnetcore-security
• GitHub Login: @Rick-Anderson
• Microsoft Alias: riande

[Rick-Anderson]

@serpent5 I thought we updated this but must have been another doc.

[Rick-Anderson]

@IGx89 Was this addressed in https://github.com/aspnet/AspNetCore.Docs/pull/15103/files - which got brought over to #15120
cc @damienbod

[IGx89]

Not that I could see. That seemed to be focused on updating just the sample app, which doesn't access the MVC request context anywhere.

[serpent5]

This is being discussed in #12564. There's some sample code in a draft PR against that issue, but it's awaiting feedback on whether or not that is the recommended approach.

[Rick-Anderson]

Draft PR being #15218

[IGx89]

Thanks! I'll add a comment on that PR with an example. So far from playing with its code, it doesn't appear to demonstrate a way to access RouteData yet.

[Rick-Anderson]

Moved to #16191