🎩 What? Why?

Fixes invalid signature issues with decrypting non-encrypted data on installations that have been generated prior to Rails 5.2.

For pre-Rails 5.2 installations or installations that get their configuration defaults from Rails 5.1, the message decryption can fail due to ActiveSupport::MessageVerifier::InvalidSignature.

This happens in case you have the following configuration option in one of your initializers (or environment configuration):

Rails.application.config.active_support.use_authenticated_message_encryption = false

Alternatively, it can also happen if you have the following in your instance's config/application.rb because this was the default configuration for pre-Rails 5.2:

module DecidimAwesomeTown
  class Application < Rails::Application
    # ...
    config.load_defaults 5.1
    # ...
  end
end

📌 Related Issues

• Related to Encrypt authorization metadata #6947
• Fixes Can't migrate the DB after #6947 #7487

Testing

• Create a 0.23 installation
• Make sure you use the explained configurations (e.g. config.load_defaults 5.1 in config/application.rb)
• Create the database, run the migrations for 0.23 and create the seed data
• Run the following query in the console: Decidim::Authorization.create!(user: Decidim::User.first, name: "postal_code", metadata: {}, verification_metadata: { address: "Awesome street 1", verification_code: "12345", letter_sent_at: Time.current })
• Upgrade the instance to 0.24.0.rc1
• Run the migrations
• See the error in the console.

📋 Checklist

• ❓ CONSIDER adding a unit test if your PR resolves an issue.
• ✔️ DO check open PR's to avoid duplicates.
• ✔️ DO keep pull requests small so they can be easily reviewed.
• ✔️ DO build locally before pushing.
• ✔️ DO make sure tests pass.
• ✔️ DO make sure any new changes are documented in docs/.
• ✔️ DO add and modify seeds if necessary.
• ✔️ DO add CHANGELOG upgrade notes if required.
• ✔️ DO add to GraphQL API if there are new public fields.
• ✔️ DO add link to MetaDecidim if it's a new feature.
• ❌AVOID breaking the continuous integration build.
• ❌AVOID making significant changes to the overall architecture.