fix: account token encryption/decryption #2421
Merged
+77
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Resolves #2420
Even though we've had this migration code since v6.0.0, upon closer inspection we were previously only migrating on-startup in memory and never persisting back to storage (oops).
This should restore the migration logic, and importantly, persist the encrypted token back to disk for next time.
Also adds similar logic to write back refreshed accounts to local storage