[NIFI-6994] Handle flowfile repository encryption status change on startup

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 1.2.0
• Component/s: Core Framework
• Labels: encryption provenance security
• Assignee: Unassigned
• Reporter: Andy LoPresto
• Created: 08/Jan/20 22:02
• Updated: 06/Jul/24 15:40
• Resolved: 06/Jul/24 15:40

Description

If the flowfile repository changes from encrypted -> unencrypted or vice-versa on startup, the application should handle the change.

• Unencrypted -> encrypted: This is handled by default for SequentialAccessWriteAheadLog -> EncryptedSequentialAccessWriteAheadLog, but RocksDBFlowFileRepository and MinimalLockingWriteAheadLog are not yet covered.
• Encrypted -> unencrypted: Detect encrypted flowfile records and change SerDeFactory logic to instantiate encrypted serde for decrypt during initial recovery only. This depends on the key(s) for the key IDs used still being available via nifi.properties.

This process may be very slow given large existing repositories, so a standalone tool should also be made available to perform this process outside of the running app.

Issue Links

• is a clone of: NIFI-6783 Handle content repository encryption status change on startup