Success! With Andrea’s help, we finally resolved the login session issue that had been causing trouble for the past two days. After reviewing the current session strategy, we decided to move away from the PropertySession method.
Instead, we implemented a CacheSession approach that allowed us to store user session data more reliably. This solution keeps the session active for up to 24 hours unless the user manually logs out, improving both usability and stability.
This change made a huge difference. Users can now log in once and stay authenticated throughout their session without interruption. We also updated the logic to refresh the cache on activity, which helps maintain continuity across tabs.
Andrea and I ran a series of tests to ensure the session behavior was consistent under different scenarios, including incognito browsing, tab duplication, and idle periods. Everything worked as expected.
With this milestone complete, the login flow is now much more robust and user-friendly. It’s rewarding to see a nagging issue finally come to a satisfying conclusion through teamwork and iteration.