Use URL-safe CSRF tokens and SameSite in cookies
These measures increase protection against CSRF ataks. The only reason Rails provides them as a configuration option is there are complex applications that run one version of the code in some servers while running an old version of the code in other servers might run into issues because the the old version won't handle the tokens or cookies generated by the new version. Since most Consul applications use just one server and the ones with more servers would only face this issue for a few seconds (while upgrading to a new version of Consul Democracy), we can safely enable these configuration options.
This commit is contained in:
@@ -23,13 +23,13 @@ Rails.application.config.active_job.skip_after_callbacks_if_terminated = true
|
||||
#
|
||||
# This change is not backwards compatible with earlier Rails versions.
|
||||
# It's best enabled when your entire app is migrated and stable on 6.1.
|
||||
# Rails.application.config.action_dispatch.cookies_same_site_protection = :lax
|
||||
Rails.application.config.action_dispatch.cookies_same_site_protection = :lax
|
||||
|
||||
# Generate CSRF tokens that are encoded in URL-safe Base64.
|
||||
#
|
||||
# This change is not backwards compatible with earlier Rails versions.
|
||||
# It's best enabled when your entire app is migrated and stable on 6.1.
|
||||
# Rails.application.config.action_controller.urlsafe_csrf_tokens = true
|
||||
Rails.application.config.action_controller.urlsafe_csrf_tokens = true
|
||||
|
||||
# Specify whether `ActiveSupport::TimeZone.utc_to_local` returns a time with an
|
||||
# UTC offset or a UTC time.
|
||||
|
||||
Reference in New Issue
Block a user