Client searching and "client configuration validation" runs multiple times, and produces 10 SQL queries via EF each run about identityserver HOT 4 CLOSED

Have you turned on caching for the client store?

https://docs.duendesoftware.com/identityserver/v5/data/configuration/#caching-configuration-data

from identityserver.

Ahh, missed that part of the documentation when I configured EF operation stores. So I added this:

builder.AddConfigurationStoreCache();

and slowness and queries did go away. It doesn't even produce the client configuration validation logs any more.

I'm still curious on why it would perform those validations against database so many times without caching (I guess it's some low level internal implementations/verifications for security?), and why the default EF ClientStore was written to do 10 individual queries instead of one Include/join.

from identityserver.

The internal implementation is data access agnostic. That's why you can "decorate" your data store with a cache.

from identityserver.

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue.

from identityserver.