Revise IAuthorizationRequirementData article details

[guardrex]

Fixes #37340

Updates the Security-node article to clarify that the IAuthorizationRequirementData interface isn't supported in Razor components, hubs, and AuthorizeFilters. I also adjusted the sample app description, specifying it uses a Minimal API endpoint.

Side Note: I see new API coming for .NET 11+, and we'll take care of that later. For now, I'm just trying to get the phrasing of these remarks correct.

I originally created the BWA to only demonstrate use with a Minimal API endpoint ...

• https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/security/authorization/AuthRequirementsDataBWA/Authorization/MinimumAgeAuthorizeAttribute.cs
• https://github.com/dotnet/AspNetCore.Docs.Samples/blob/main/security/authorization/AuthRequirementsDataBWA/Program.cs#L35-L38

... using the same AuthorizationHandler that I found in the original MVC sample.

Is the BWA implementation a sensible demo?

Also, can you take a look at the original MVC sample, which now accompanies the new MVC authz node article?

In the MVC sample ...

• MinimumAgeAuthorizeAttribute
• MinimumAgeAuthorizationHandler
• Program
• GreetingsController

Similar question, given that it's demoed with an AuthorizationHandler, which is what I assume makes it work with a controller. I need guidance from you on how to phrase the support remark in the MVC article, unless you just want to stick with what we're placing in the main article.

---

Internal previews

📄 File	🔗 Preview link
aspnetcore/security/authorization/custom-authorization-policies-with-iauthorizationrequirementdata.md	aspnetcore/security/authorization/custom-authorization-policies-with-iauthorizationrequirementdata