Question: does EF core store use caching?

[kirill-gerasimenko-da]

Hi!

I've started using the project and doing some experiments under the load, and the access time for the current keys to generate the token caught my attention and I've started digging. So I noticed that here

Security.Jwt/src/NetDevPack.Security.Jwt.Store.EntityFrameworkCore/DatabaseJsonWebKeyStore.cs

Line 64 in 5200210

return await _context.SecurityKeys.OrderByDescending(d => d.CreationDate).AsNoTrackingWithIdentityResolution().FirstOrDefaultAsync();

it does call the database, despite the cache hit. Is this something expected? I'd think that it just has to return credentials found in the memory cache at this point. To compare - I've checked with file system store implementation - and it works as I would expect, returning credentials found in the memory cache.

Please advise.

Thanks for the great library!

[kirill-gerasimenko-da]

I'm willing to put a PR up, if necessary :)

[brunobritodev]

Definetely, this code doesnt make sense, it should return from cache instead take it again from database.

A PR will be welcome!

[kirill-gerasimenko-da]

Great!

I've got weird issue with the change I'm making - the file I'm changing is in UTF-16LE encoding, and it gets recognized as binary by GitHub. I tried to do changes directly in GitHub, but with the same results. I'll try to work around this.

[kirill-gerasimenko-da]

Like in here kirill-gerasimenko-da@bd8c167?diff=split#diff-02a402020f707191067d8e3ea8f99d6b1128292d2975d300001beeb37134ae49 - file is shown as binary, but if you open it up - it works and has the changes, weird.

[kirill-gerasimenko-da]

#41

[github-actions]

🎉 This issue has been resolved in version 7.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀