Skip to content

Encrypt static_object_token_encrypted field via background migration

Vasilii Iakliushin requested to merge 348163_migrate_static_object_token into master

What does this MR do and why?

Contributes to #348163 (closed)

Roadmap

  1. Add database fields for encrypted tokens - !75426 (merged)
  2. Migrate old tokens to encrypted version and start using them <- This MR
  3. Drop plaintext token fields - #348426

Problem

We store static_object_token values in plaintext.

Solution

  • Fill static_object_token_encrypted fields with a background migration
  • Use optional (encrypted first, plaintext is a fallback) strategy
  • Store encrypted version of the token when user updates it

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Vasilii Iakliushin

Merge request reports