feat(socket): notify drivers on JWT expiration during active WebSocket session - #166
Merged
Conversation
- Fix authService.verifyToken to check decoded.userId first - Store raw JWT token on socket.data during connection handshake - Add SocketService.validateSocketToken for DB-backed token validation - Implement setupTokenExpirationCheck in locationHandler: - Periodic JWT validation on configurable interval (default 60s) - Emit auth_expired event with grace period (default 30s) - Handle auth_refresh to accept new JWT without reconnecting - Graceful disconnect if token not refreshed in time - Extend socket.types with AuthExpiredPayload, AuthRefreshPayload, etc. - Add unit tests for validateSocketToken and token expiration flow
…-location-updates-to-silently-fail-mid-delivery
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
closes #151
Summary
Ensures drivers are notified when their JWT token expires during an active WebSocket session. The server now periodically validates the token, emits an auth_expired event to prompt the client to refresh, and gracefully disconnects if the token is not refreshed in time.
Changes Made
Modified files:
New files: