Repository encryption migration

This feature helps the administrator retroactively encrypt content that was saved before the repository.content.encryption configuration property was turned on, or while it was temporarily off, for each row independently:

• Content: document content and extracted text (DATASTORE, EXTRACTION).
• Cache: PDF, SVG, and mail preview cache (PDF, SVG, MAIL).

Note

This migration is optional: content that predates encryption being turned on is already handled transparently and stays fully readable and usable without running it.

Repository Encryption Migration is shown in a table, one row per Type/Kind, with its status (Never run, Running, or Finished) and counters: Found, Encrypted, Already encrypted, and Errors.

Run a migration

• Click the Start button for the desired row.

Caution

Each row runs independently and only one migration per row can run at a time. The migration runs in the background and can take minutes or hours, depending on the volume of data. The progress page refreshes automatically every two seconds, showing the same counters plus Bytes encrypted, the current tenant/shard being processed, and the last error.

Note

The detailed log can also be followed on the progress page, filtered by ContentEncryptionMigrator (Content rows) or CacheEncryptionMigrator (Cache rows).