>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #2924957. --> Reported by: [thecraighammond](https://www.drupal.org/user/3144891) >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Currently nested fields (such as Address) where multiple values are allowed do not encrypt. Encryption of elements with nested fields only works to one level and where the maximum number of values is one. This becomes a problem for both elements with multiple values allowed or custom elements (that could have fields nested to multiple levels and have multiple allowed values).</p> <p><img src="https://www.drupal.org/files/issues/Capture_188.JPG" alt="Nested values encryption failure example"></p> <p>The above screenshot highlights how single value nested fields encrypt correctly (test_address_field) but elements where multiple values are allowed (test_multiple_address_field) do not retain values - in this example there was one of a possible 10 addresses added to the form submission.</p> <p>Below shows the original data for the submission - note that the text_multiple_address_field has data (nested) for the first set of values. This is lost after encryption, as seen above.</p> <p><img src="https://www.drupal.org/files/issues/Capture2_22.JPG" alt="Nested values encryption failure example"></p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Encrypt functionality needs to recursively encrypt element's fields from top level down taking into account the additional array key for each (set of) values for both the included elements types (e.g. Address) and any custom elements. Custom elements could also have multiple levels of nesting.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <p>Recursively encrypt nested fields.</p> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <ul> <li>Several new methods to WebformEncryptSubmissionStorage.</li> <li>Removal of WebformEncryptSubmissionStorage::getDecryptedData()</li> <li>Stop using hook_entity_presave()</li> </ul> <h3 id="summary-data-model-changes">Data model changes</h3> <p>(Database or configuration data changes that would make stored data on an existing site incompatible with the site's updated codebase, including changes to hook_schema(), configuration schema or keys, or the expected format of stored data, etc.)</p> <h3 id="summary-original-report">Original report by [username]</h3> <p>N/A</p>