aspnet/Blazor

@optimizasean I think I found a way to get your navigationmanager based policy to work - maybe, but only by using RequireAssertion.

Your comment about NavigationManager being "stuck" was, I think, slightly off - it's the RequireClaim that gets "stuck" - it is only evaluated at startup, so only returns resource Ids for the base url (or whatever url you first load)

RequireAssertion uses a Func that is called every time the policy is checked, so in there you can happily reference the current URL and check the claims.

This was just a quick test to see if it works - and it does - not saying that checking claims that way is correct, just "does it work as an idea"

Program.cs

NavigationManager navMan = default;
builder.Services.AddAuthorizationCore(options =>
{
    options.AddPolicy(Policies.CanAccessResource, builder=>Policies.CanAccessResourcePolicy(builder,navMan));
});
var app = builder.Build();
navMan = app.Services.GetRequiredService<NavigationManager>();
await app.RunAsync();

Policies.cs

public static AuthorizationPolicy CanAccessResourcePolicy(AuthorizationPolicyBuilder builder, NavigationManager navMan)
    => builder.RequireAssertion(context => {
        var resourceIds = GetResourceValues(new List<int>() { 2, 3, 5, 6 }, navMan);
        return context.User.HasClaim(claim =>
            claim.Type == "ResourceName" && resourceIds.Contains(claim.Value)
            );
        }).Build();