Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 12-9-stable
  • 12-7-stable
  • 12-6-stable
  • 12-8-stable
  • github/fork/Kloppi313/patch-1
  • 12-5-stable
  • 12-4-stable
  • github/fork/ramalokesh8477/master
  • 12-1-stable
  • 12-2-stable
  • 12-0-stable
  • 12-3-stable
  • 42-42-stable
  • github/fork/hussamgit398/patch-2
  • 12-3-auto-deploy-20190911
  • 12-3-auto-deploy-20190916
  • 12-3-auto-deploy-20190908
  • 12-3-auto-deploy-20190901
  • 12-3-auto-deploy-20190901-32664
  • v12.10.0.pre
  • v12.9.0
  • v12.9.0-rc42
  • v12.8.7
  • v12.8.6
  • v12.8.5
  • v12.8.4
  • v12.8.3
  • v12.6.8
  • v12.7.7
  • v12.8.2
  • v12.8.1
  • v12.9.0.pre
  • v12.8.0
  • v12.8.0-rc42
  • v12.5.10
  • v12.7.6
  • v12.6.7
  • v12.7.5
  • v12.5.9
40 results

application_setting.rb

  • Arturo Herrero's avatar
    a3f16b6b
    Encrypt application setting tokens · a3f16b6b
    Arturo Herrero authored
    This is the plan to encrypt the plaintext tokens:
    
    First release (this commit):
      1. Create new encrypted fields in the database.
      2. Start populating new encrypted fields, read the encrypted fields or
         fallback to the plaintext fields.
      3. Backfill the data removing the plaintext fields to the encrypted fields.
    
    Second release:
      4. Remove the virtual attribute (created in step 2).
      5. Drop plaintext columns from the database (empty columns after step 3).
    a3f16b6b
    History
    Encrypt application setting tokens
    Arturo Herrero authored
    This is the plan to encrypt the plaintext tokens:
    
    First release (this commit):
      1. Create new encrypted fields in the database.
      2. Start populating new encrypted fields, read the encrypted fields or
         fallback to the plaintext fields.
      3. Backfill the data removing the plaintext fields to the encrypted fields.
    
    Second release:
      4. Remove the virtual attribute (created in step 2).
      5. Drop plaintext columns from the database (empty columns after step 3).