server
server copied to clipboard
fix: token LocalCache to DistributedCache
Fix #46165
In a load-balanced platform with multiple application servers, local token caching does not work effectively and leads to login loops. We believe that by making this change, we can use a distributed cache instead.
- Resolves: In a load-balanced platform without sticky sessions, local token caching does not work and causes a login loop.
Summary
Currently, the token is stored in the local cache. In the case of a load-balanced Nextcloud platform without Sticky Sessions, it is necessary to store the token in the distributed cache if it exists.
Checklist
- Code is properly formatted
- Sign-off message is added to all commits