AspNet.Security.OpenIdConnect.Server | OpenID Connect/OAuth2 server framework | OAuth library
kandi X-RAY | AspNet.Security.OpenIdConnect.Server Summary
kandi X-RAY | AspNet.Security.OpenIdConnect.Server Summary
OpenID Connect/OAuth2 server framework for OWIN/Katana and ASP.NET Core
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of AspNet.Security.OpenIdConnect.Server
AspNet.Security.OpenIdConnect.Server Key Features
AspNet.Security.OpenIdConnect.Server Examples and Code Snippets
Community Discussions
Trending Discussions on AspNet.Security.OpenIdConnect.Server
QUESTION
After migrating from .NET Core 2.2 to 3.1, EF Core will randomly start crawling Users-table and make hundreds/thousands of logs (see picture - specific log is in bottom highlighted with blue).
I have followed migration guides from Microsoft, e.g. 2.2 to 3.0 and 3.0 to 3.1. (Example: https://docs.microsoft.com/da-dk/aspnet/core/migration/22-to-30?view=aspnetcore-2.1&tabs=visual-studio).
Important info: This has started happening after I added app.UseAuthorization();
in Startup.cs
, which wasn't there before.
Any ideas what could trigger this?
It results in the following error after maybe 30 seconds: 504 Gateway Time-out
I am using NuGet AspNet.Security.OpenIdConnect.Server
.
Update Seems to happen on Microsoft.EntityFrameworkCore.DbUpdateConcurrencyException: Database operation expected to affect 1 row(s) but actually affected 0 row(s).
So eradicating that exception should fix it, but I would be very careful to push this migration to the production server, if somehow an exception can cause EF Core to start crawling endlessly.
ANSWER
Answered 2021-Nov-24 at 08:54The problem was when using Serilog to log exceptions with destructureObjects
set to true, for some reason. So when an exception was caught in a try-catch
and then logged with destructureObjects
set to true, it started to crawl endlessly.
QUESTION
I'm using OpenIdDict library for OpenId server. Everything worked perfectly when I was in EST (-5h) time zone. But when I moved to UTC+03 time zone I'm constantly getting an error:
OpenIddict.Server.Internal.OpenIddictServerHandler: Error: The token request was rejected because the authorization code or the refresh token was expired.
exactly on the same code. The error occurs when I call token exchange endpoint. I checked database and all values there seems to be correct UTC values.
I found that the error was fired at AspNet.Security.OpenIdConnect.Server\src\AspNet.Security.OpenIdConnect.Server\OpenIdConnectServerHandler.Exchange.cs. But I'm not sure how to debug it.
...ANSWER
Answered 2020-Sep-25 at 07:53The reason of the bug is pretty old issue in Oracle MySql driver https://bugs.mysql.com/bug.php?id=92367. If you faced the same problem you can find pretty good explanation and workaround here: https://github.com/openiddict/openiddict-core/issues/1097#issuecomment-698374105. For now the best solution seems to be switching to the Pomelo driver: https://www.nuget.org/packages/Pomelo.EntityFrameworkCore.MySQL
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install AspNet.Security.OpenIdConnect.Server
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page