-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes you made to Startup.cs cause below error #220
Comments
line 138 |
Hi
Ok thanks for the info
Peter
… On 3 Mar 2019, at 16:18, Marek Fišera ***@***.***> wrote:
Hi @PeterJD <https://github.com/PeterJD>.
I know that, all commits related to the #218 <#218> are work in progress.
I'm going to completely remove the Money.UI.Backend and advance to an api-centric version, in the Money.Api.
If you want latest working version, please use tag blazor-v1.7.0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#220 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFpv3-84xNYb3BFrW7yHamGytxG4klb1ks5vS_XSgaJpZM4bbErd>.
|
I'm going to close this one. If you have any further questions, feel free to ask. |
What is the solution? |
We don't use cookies for a long time. When code was migrated to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Money.UI.Backend
An unhandled exception occurred while processing the request.
InvalidOperationException: No authentication handler is registered for the scheme 'Cookies'. The registered schemes are: Bearer, Identity.Application, Identity.External, Identity.TwoFactorRememberMe, Identity.TwoFactorUserId. Did you forget to call AddAuthentication().AddSomeAuthHandler?
Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, string scheme, AuthenticationProperties properties)
Stack Query Cookies Headers
InvalidOperationException: No authentication handler is registered for the scheme 'Cookies'. The registered schemes are: Bearer, Identity.Application, Identity.External, Identity.TwoFactorRememberMe, Identity.TwoFactorUserId. Did you forget to call AddAuthentication().AddSomeAuthHandler?
Microsoft.AspNetCore.Authentication.AuthenticationService.ChallengeAsync(HttpContext context, string scheme, AuthenticationProperties properties)
Money.Startup+<>c+<b__5_2>d.MoveNext() in Startup.cs
+
await context.ChallengeAsync(CookieAuthenticationDefaults.AuthenticationScheme);
Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.StatusCodePagesMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.Invoke(HttpContext context)
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.Invoke(HttpContext httpContext)
Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)
The text was updated successfully, but these errors were encountered: