Skip to content

fix: scope session cookie name per instance to prevent CSRF 422s #364

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
MatthewSuttles merged 1 commit into from
Jun 23, 2026
+12 −0
Merged

fix: scope session cookie name per instance to prevent CSRF 422s #364

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions config/initializers/session_store.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
# Scope the session cookie name to this instance so multiple Hivemind
# instances can coexist on one host. Browsers share cookies across ports
# for the same host (localhost:8080 and localhost:8081 share a jar), so a
# shared cookie name would let instances overwrite each other's session —
# producing "Can't verify CSRF token authenticity" 422s on sign-in.
#
# COMPOSE_PROJECT_NAME is unique per instance ("hivemind" for the primary,
# "hivemind-<name>" for instances created via `hivemind new`). The primary
# keeps the historical "_hivemind_session" key via the default fallback, so
# existing sessions are not invalidated.
Rails.application.config.session_store :cookie_store,
key: "_#{ENV.fetch('COMPOSE_PROJECT_NAME', 'hivemind')}_session"
Loading