-
Notifications
You must be signed in to change notification settings - Fork 75
Open
Description
After successfully logging in with bob/Alice and "My long 123$ password", it just sits on the login page.
I see the following in the Asp.Net Core Web Server output window:
[20:23:42 Debug] IdentityServer4.Startup
Error Id Parameter: errorId
[20:23:57 Information] Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler
AuthenticationScheme: Identity.Application was challenged.
[20:24:06 Debug] IdentityServer4.Hosting.CorsPolicyProvider
CORS request made for path: /Account/Login from origin: null but was ignored because path was not for an allowed IdentityServer CORS endpoint
[20:24:15 Debug] IdentityServer4.Hosting.IdentityServerAuthenticationService
Augmenting SignInContext
[20:24:15 Debug] IdentityServer4.Hosting.IdentityServerAuthenticationService
Adding idp claim with value: local
[20:24:15 Debug] IdentityServer4.Hosting.IdentityServerAuthenticationService
Adding auth_time claim with value: 1639013055
[20:24:15 Information] Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler
AuthenticationScheme: Identity.Application signed in.
[20:24:15 Information] IdentityServer4.Events.DefaultEventService
{"Username": "bob", "Provider": null, "ProviderUserId": null, "SubjectId": "861cd41e-b812-4f88-a386-8118d8b832b4", "DisplayName": "bob", "Endpoint": "UI", "ClientId": null, "Category": "Authentication", "Name": "User Login Success", "EventType": "Success", "Id": 1000, "Message": null, "ActivityId": "80000004-0002-f800-b63f-84710c7967bb", "TimeStamp": "2021-12-09T01:24:15.0000000Z", "ProcessId": 8472, "LocalIpAddress": "::1:5000", "RemoteIpAddress": "::1", "$type": "UserLoginSuccessEvent"}
[20:24:15 Information] Microsoft.AspNetCore.Authentication.Cookies.CookieAuthenticationHandler
AuthenticationScheme: Identity.Application was challenged.
The line I'm curious about is:
CORS request made for path: /Account/Login from origin: null but was ignored because path was not for an allowed IdentityServer CORS endpoint
I'm wondering if it's failing because of this. Or does anybody have an idea what could be wrong?
Thanks!
Metadata
Metadata
Assignees
Labels
No labels