Skip check_session_expiry in SessionsController#70
Closed
JuanVqz wants to merge 1 commit intofix-brakemanfrom
Closed
Skip check_session_expiry in SessionsController#70JuanVqz wants to merge 1 commit intofix-brakemanfrom
JuanVqz wants to merge 1 commit intofix-brakemanfrom
Conversation
SessionsController skipped check_user_token but not check_session_expiry, so users with an expired session were shown the login page instead of completing the OAuth callback flow.
JuanVqz
added a commit
that referenced
this pull request
Mar 6, 2026
Replaces #66, #67, #68, #70 with a single cohesive fix: - Merge check_session_expiry + check_user_token into one authenticate! callback, eliminating the double-render risk by design - SessionsController and Slack::ApplicationController now each skip a single authenticate! instead of managing multiple callbacks - Rename valid_slack_request? to verify_slack_request! and make it halt with head :unauthorized when signature verification fails - Replace head :unprocessable_entity in send_message with logging and Sentry.capture_exception so notification failures never affect the HTTP response back to Slack
Member
Author
|
Superseded by #71 which addresses this and three other related bugs with a more robust design. |
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.
Problem
SessionsControllerskippedcheck_user_tokenbut notcheck_session_expiry, leaving a gap in the auth filter setup. Both callbacks are defined inApplicationControllerand both need to be skipped on the OAuth endpoint:As a result, a user whose session had expired would hit
check_session_expirybefore reachingSessionsController#create. The callback resets the session and renderspuzzles/login, so the OAuth flow never completes — the user can't log back in.This is a particularly bad failure mode: it's triggered exactly when the user needs to re-authenticate, making it impossible to recover a session through normal login.
Fix
Add the missing
skip_before_actionalongside the existing one:Test
The test signs in (establishing a session with
expires_at), then usestravel_toto jump 2 hours into the future so the session is expired. A second sign-in attempt then asserts a redirect toroot_path, confirming the OAuth callback completes instead of being blocked.