-
Notifications
You must be signed in to change notification settings - Fork 0
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
Hitting .well-known/openid-configuration endpoint leads to memory leak #1397
Comments
Thanks for sharing these details. We have another issue that we are working on that gives timeouts on the discovery endpoint. I wounder if this could actually be the same issue. The memory leakage could be an early indication that something is wrong and then it would eventually freeze. Could you please check your dependencies according to the notes in #1361 (comment)? |
We do not have dependency on "Azure.Extensions.AspNetCore.DataProtection.Keys", But have dependency on "Azure.Identity" (1.12.0) and "Azure.Core" (1.41.0). |
Our configurations are not dynamic. Is it possible to cache the response? The current code prepares /.well-known response by adds lots of entries to a Dictionary<string, object> and then serializing it to Json. |
The issue is in Azure.Core version 1.41.0 and prior, could you please try updating Azure.Core to 1.42.0? There is o new |
Which version of Duende IdentityServer are you using?
7.0.6
Which version of .NET are you using?
8.0
Describe the bug
If hit /.well-known/openid-configuration multiple times it leads to memory leak.
Server is configured as follows
To Reproduce
Steps to reproduce the behavior.
Expected behavior
No memory leak should be observed.
Kindly let me know if there is any to way cache the output, and why adding
AddInMemoryCaching
is not sufficient.The text was updated successfully, but these errors were encountered: