Mirroristas/CommunitySolidServer
2
0
Fork 0
mirror of https://github.com/CommunitySolidServer/CommunitySolidServer.git synced 2024-10-03 14:55:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat: Add migration for v6 account data

Browse Source
This commit is contained in:
Joachim Van Herwegen
2023-10-04 16:38:46 +02:00
parent fedd9e04d8
commit 0ac7d407bf
39 changed files with 1034 additions and 89 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
documentation/markdown/usage/account/migration.md
View File

@@ -26,12 +26,9 @@ Additionally to the details below, the tail of all resource identifiers were bas
* Resource identifiers: the token label
* Data format: `{ webId, secret }`
The best way to migrate the data would be to read in the old data,
and make use of the new classes to generate the new account objects,
as generating the data manually might be too cumbersome.
Ideally the account classes of the previous version can be reused to read in the older data
to prevent having to read the old data directly.
During migration, WebID ownership validation would need to be disabled
as otherwise the server won't allow linking the WebIDs.
The password values can be reused as the password storage method was not changed.
The `V6MigrationInitializer` class is responsible for migrating from this format to the new one
and does so by reading in the old data and creating new instances in the `IndexedStorage`.
In case you have an instance that made impactful changes to how storage is handled
that would be the class to investigate and replace.
Password data can be reused as the algorithm there was not changed.
Email addresses are now stored in lowercase, so these need to be converted during migration.