Question, we've been working on migrating an app for a long time and we're getting there (takes a long to migrate from .NET 4.8 to this solution) but one issue we disagree on is where to store user-session-related information.
For example, in the app a user has a bit of a state that gets set as they move through the app. We don't want to include that state in the query string (stateless) as it would be too cumbersome. In the old app we stored it in session but we're not sure that's the correct way to go about it.
We just tried adding a claim to store that information but because the value(s) can change so frequently, we're not sure that's a good solution either.
Any ideas? We want to make sure whatever solution we use is compatible with scaling the system horizontally in the future as we're dealing with large user loads.
1 Answer(s)
-
0
Hi,
We just tried adding a claim to store that information but because the value(s) can change so frequently, we're not sure that's a good solution either.
Not suitable for storing frequently changing information, like the JWT token is immutable, when you change a claim, you must get a new token.
How about using the Distributed cache: https://docs.abp.io/en/abp/latest/Caching
