rails/activesupport/lib/active_support/message_verifiers.rb
Jonathan Hefner 61f711a1ff Support Message{Encryptors,Verifiers}#rotate block
This commit adds a block form of `ActiveSupport::MessageEncryptors#rotate`
and `ActiveSupport::MessageVerifiers#rotate`, which supports
fine-grained per-salt rotation options.  The block will receive a salt,
and should return an appropriate options Hash.  The block may also
return `nil` to indicate that the rotation does not apply to the given
salt.  For example:

  ```ruby
  verifiers = ActiveSupport::MessageVerifiers.new { ... }
  verifiers.rotate(serializer: JSON, url_safe: true)
  verifiers.rotate do |salt|
   case salt
   when :foo
     { serializer: Marshal, url_safe: true }
   when :bar
     { serializer: Marshal, url_safe: false }
   end
  end

  # Uses `serializer: JSON, url_safe: true`.
  # Falls back to `serializer: Marshal, url_safe: true`.
  verifiers[:foo]

  # Uses `serializer: JSON, url_safe: true`.
  # Falls back to `serializer: Marshal, url_safe: false`.
  verifiers[:bar]

  # Uses `serializer: JSON, url_safe: true`.
  verifiers[:baz]
  ```

This can be particularly useful when migrating older configurations to a
unified configuration.
2022-12-19 16:35:20 -06:00

135 lines
4.9 KiB
Ruby

# frozen_string_literal: true
require "active_support/messages/rotation_coordinator"
module ActiveSupport
class MessageVerifiers < Messages::RotationCoordinator
##
# :attr_accessor: transitional
#
# If true, the first two rotation option sets are swapped when building
# message verifiers. For example, with the following configuration, message
# verifiers will generate messages using <tt>serializer: Marshal, url_safe: true</tt>,
# and will able to verify messages that were generated using any of the
# three option sets:
#
# verifiers = ActiveSupport::MessageVerifiers.new { ... }
# verifiers.rotate(serializer: JSON, url_safe: true)
# verifiers.rotate(serializer: Marshal, url_safe: true)
# verifiers.rotate(serializer: Marshal, url_safe: false)
# verifiers.transitional = true
#
# This can be useful when performing a rolling deploy of an application,
# wherein servers that have not yet been updated must still be able to
# verify messages from updated servers. In such a scenario, first perform a
# rolling deploy with the new rotation (e.g. <tt>serializer: JSON, url_safe: true</tt>)
# as the first rotation and <tt>transitional = true</tt>. Then, after all
# servers have been updated, perform a second rolling deploy with
# <tt>transitional = false</tt>.
##
# :method: initialize
# :call-seq: initialize(&secret_generator)
#
# Initializes a new instance. +secret_generator+ must accept a salt, and
# return a suitable secret (string). +secret_generator+ may also accept
# arbitrary kwargs. If #rotate is called with any options matching those
# kwargs, those options will be passed to +secret_generator+ instead of to
# the message verifier.
#
# verifiers = ActiveSupport::MessageVerifiers.new do |salt, base:|
# MySecretGenerator.new(base).generate(salt)
# end
#
# verifiers.rotate(base: "...")
##
# :method: []
# :call-seq: [](salt)
#
# Returns a MessageVerifier configured with a secret derived from the
# given +salt+, and options from #rotate. MessageVerifier instances will
# be memoized, so the same +salt+ will return the same instance.
##
# :method: []=
# :call-seq: []=(salt, verifier)
#
# Overrides a MessageVerifier instance associated with a given +salt+.
##
# :method: rotate
# :call-seq: rotate(**options)
#
# Adds +options+ to the list of option sets. Messages will be signed using
# the first set in the list. When verifying, however, each set will be
# tried, in order, until one succeeds.
#
# Notably, the +:secret_generator+ option can specify a different secret
# generator than the one initially specified. The secret generator must
# respond to +call+, accept a salt, and return a suitable secret (string).
# The secret generator may also accept arbitrary kwargs.
#
# If any options match the kwargs of the operative secret generator, those
# options will be passed to the secret generator instead of to the message
# verifier.
#
# For fine-grained per-salt rotations, a block form is supported. The block
# will receive the salt, and should return an appropriate options Hash. The
# block may also return +nil+ to indicate that the rotation does not apply
# to the given salt. For example:
#
# verifiers = ActiveSupport::MessageVerifiers.new { ... }
#
# verifiers.rotate do |salt|
# case salt
# when :foo
# { serializer: JSON, url_safe: true }
# when :bar
# { serializer: Marshal, url_safe: true }
# end
# end
#
# verifiers.rotate(serializer: Marshal, url_safe: false)
#
# # Uses `serializer: JSON, url_safe: true`.
# # Falls back to `serializer: Marshal, url_safe: false`.
# verifiers[:foo]
#
# # Uses `serializer: Marshal, url_safe: true`.
# # Falls back to `serializer: Marshal, url_safe: false`.
# verifiers[:bar]
#
# # Uses `serializer: Marshal, url_safe: false`.
# verifiers[:baz]
##
# :method: rotate_defaults
# :call-seq: rotate_defaults
#
# Invokes #rotate with the default options.
##
# :method: clear_rotations
# :call-seq: clear_rotations
#
# Clears the list of option sets.
##
# :method: on_rotation
# :call-seq: on_rotation(&callback)
#
# Sets a callback to invoke when a message is verified using an option set
# other than the first.
#
# For example, this callback could log each time it is called, and thus
# indicate whether old option sets are still in use or can be removed from
# rotation.
private
def build(salt, secret_generator:, secret_generator_options:, **options)
MessageVerifier.new(secret_generator.call(salt, **secret_generator_options), **options)
end
end
end