jaeyun0503 commented on issue #3737: URL: https://github.com/apache/texera/issues/3737#issuecomment-3325950685
> [@Sentiaus](https://github.com/Sentiaus) Thanks for the comments. We had an internal discussion about the two designs and came up with a solution. [@jaeyun0503](https://github.com/jaeyun0503) : please chime in with our decision. It will be good for [@Sentiaus](https://github.com/Sentiaus) to verify our decision. Yes. We had an internal discussion on this Issue and we decided to go with Design 2 and use three PRs to address this and Issue #3738: 1. Keep the token expiration parameter, remove the refresh logic (token expiration time - 1): We wanted to implement design 2 to get rid of the token refresh interval, and use the token expiration parameter to define a user's expiration token interval (the proposed interval is 7 days). 2. When user talk to backend with an expired token, backend should return 401 and frontend should always clear cache: 3. (Design not finalized) When frontend talks to the backend (preferably the time it gets the token), ask for the expiration date of the token and set a timer, when the timer expires clear up the frontend cache For the context of Bullet points 2 and 3, you can take a look at #3738 as we explained the reason behind the issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
