You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
This would make the multiple identities scenarios easier, as a dev could set the default behaviour to use Cookie auth, which in turn would mean you wouldn't have to set cookie auth to be automatic, and filtering would work as expected when you limit to bearer.
The text was updated successfully, but these errors were encountered:
Looks like this behavior actually comes from Policy.Combine, where we add RequireAuthenticatedUser by default.
How about we just add a default policy to the options which we use for this instead? The default behavior would be the same, just requiring any authenticated user.
You could replace it via
services.ConfigureAuthorization(options => options.DefaultPolicy = new PolicyBuilder().AddWhatever().Build())
This would make the multiple identities scenarios easier, as a dev could set the default behaviour to use Cookie auth, which in turn would mean you wouldn't have to set cookie auth to be automatic, and filtering would work as expected when you limit to bearer.
The text was updated successfully, but these errors were encountered: