Currently, the default cache ignores user context and does not account for authorization. Implementing personalized caching requires writing a custom key function for every service to extract data from the token.
Proposal:
Provide a built-in way to inject token/user information directly into cache keys to ensure secure per-user caching by default.
Currently, the default cache ignores user context and does not account for authorization. Implementing personalized caching requires writing a custom key function for every service to extract data from the token.
Proposal:
Provide a built-in way to inject token/user information directly into cache keys to ensure secure per-user caching by default.