If the CPU usage is too high, login authorization will fail.
netnr opened this issue · comments
Is there an existing issue for this?
- I have searched the existing issues
Describe the bug
<PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="7.0.19" />
Microsoft.AspNetCore.Authentication.Cookies
Both authorizations appear
Response time does not exceed 5 seconds
Expected Behavior
No response
Steps To Reproduce
No response
Exceptions (if any)
No response
.NET Version
7.0.19
Anything else?
No response
Anything could fail or take too long if the machine is under stress from high CPU usage. If the CPU is saturated the code can't force itself to succeed in less than 5 seconds.
However, judging from the previous request record time, it can respond normally in close to 8 or 10 seconds, but it fails in 125 milliseconds.
The real scenario here is that ffmpeg is called in the background to perform video slicing, and the system responds with 401
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.
When writing a reproducible example, I found that the validity period of my configuration was changed to 30 seconds.
Sorry, this is a joke
Also attached is an example, although it is of no use.
https://github.com/netnr/test/tree/main/src/Netnr.AuthFailed