Chris Sung

it seems the new 8.0 routing adds pages with [Authorization] to route, so that they have authorization metadata and can be checked with AuthorizationMiddleware if we prerender or first render...

@MackinnonBuck can we urgently have a look into this? this seems serious because Authorization in blazor is basically broken.

> @christallire How do you implement the `AuthenticationStateProvider` and do you pass your claims to it? If so, could you check whether your claims are empty or not? (edit: oh...

Well, I found a workaround by: define following class and register it where server initializes ``` public class BlazorAuthorizationMiddlewareResultHandler : IAuthorizationMiddlewareResultHandler { public Task HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy,...

I'm afraid I have to disagree that this problem can be solved with documentation.

When can we get a customized sampling feature? @fdsig sir? This is very frustrating especially when I get this:

I need this :p

Nope, need to have a different signature defined compared to no version(or version 0) like: from: ``` [Version(1)] public interface ISomeGrain : IGrainWithIntegerKey { Task Method(); Task NewMethod(int accidentParameter); }...

from ``` public interface ISomeGrain : IGrainWithIntegerKey { Task Method(); } ``` to ``` public interface ISomeGrain : IGrainWithIntegerKey { Task Method(int accidentParameter); } ``` this is re: question 2

But isn't that okay as long as agreed between both parties that are no longer the same method and both are aware of it? I was scratching my head because...