You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The class OpenIdConnectCachingSecurityTokenProvider uses read/write lock of ReaderWriterLockSlim before get issuer and keys. I am wondering, why we need to use lock here? and what happen if we don't?
The text was updated successfully, but these errors were encountered:
I've done a write-up of my findings about the locking behaviour that we're confident caused a deadlock-like situation for us under enough concurrent requests.
The class
OpenIdConnectCachingSecurityTokenProvider
uses read/write lock ofReaderWriterLockSlim
before get issuer and keys. I am wondering, why we need to use lock here? and what happen if we don't?The text was updated successfully, but these errors were encountered: