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 was archived by the owner on Dec 13, 2018. It is now read-only.
In RC2, it looks like we no longer use app.UseCookieAuthentication(options => \* ... *\); but instead app.UseIdentity();. In this case, how can I set a custom value for AccessDeniedPath?
Also, how do I prevent the cookie auth middleware from doing the redirect all together. I would like to receive a 403 when authorization fails and handle it through app.UseStatusCodePagesWithReExecute("/h/{0}").
The text was updated successfully, but these errors were encountered:
The relationship between UseCookieAuthentication and UseIdentity has not changed in RC2. If you're using the Identity components you need to use UseIdentity, which internally registers several cookie auth instances. You can configure these via:
Uh oh!
There was an error while loading. Please reload this page.
In RC2, it looks like we no longer use
app.UseCookieAuthentication(options => \* ... *\);
but insteadapp.UseIdentity();
. In this case, how can I set a custom value forAccessDeniedPath
?Also, how do I prevent the cookie auth middleware from doing the redirect all together. I would like to receive a 403 when authorization fails and handle it through
app.UseStatusCodePagesWithReExecute("/h/{0}")
.The text was updated successfully, but these errors were encountered: