Configure JWT tokens to expire after 30 seconds #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Configure JWT tokens to expire after 30 seconds
Summary
Modified the JWT token expiration configuration from 24 hours to 30 seconds in
src/backend/config.py. This changes theJWT_ACCESS_TOKEN_EXPIRESsetting to usetimedelta(seconds=30)instead oftimedelta(hours=24).All existing backend unit tests pass successfully.
Review & Testing Checklist for Human
src/frontend/src/utils/api.jsproperly clears localStorage and redirects when receiving a 401 responseNotes
src/frontend/src/utils/api.js)Link to Devin run: https://app.devin.ai/sessions/099feb22514f472aa31b01fb2bf7a877
Requested by: jia.wu@codeium.com (@JRWu)