Use auth before or after UseMultiTenant when using claims strat

[VictorioBerra]

From the docs:

Thus, the ASP.NET Core authentication middleware should still be used as normal, and in most use cases should come after UseMultiTenant.

I don't understand. If I don't put it after, I get no claims, because no auth.

Why would the docs say most cases useauth after usemulti?

[AndrewTriesToCode]

The claims strategy will still get the claim by front loading some of the behavior that authentication will use later. It caches it and the auth will reuse it rather than reprocess the cookie.

Check out the bottom of the strategy implementation, you can see where it's trigger the authentication handler to get the claim.

[VictorioBerra]

Gotcha, so I'm not using pertenantauth and instead I'm using Microsoft.Identity.Web in this example (contrary to my other issues).

When I tested I didn't get claims populated in the http context user unless I moved UseMultiTenant to after useauth