Taavi Väänänen 6ef3d2418a Database-level support for multiple auth devices ... This adds new database tables to support storing multiple authentication factors for a single user. The current approach taken is to use a single database row per 2fa method and key. The current module/key abstraction will have to be updated to support having multiple module types for a single user (for example for having a separate module for recovery codes), but this patch does not address that and instead keeps the existing limitations, however the needed updates for that should be doable with this database schema. I've decided to add a new table instead of modifying the existing oathauth_users table. This is mainly because adding an auto_increment column to the existing table would be difficult, but also allows us to update the table definition to follow MW conventions (namely the column name prefixes). I've also used the opportunity to normalize the device types onto a separate table. The migration stage variable is set to SCHEMA_COMPAT_NEW so that third-party wikis can use update.php normally and don't have to adjust anything. This means that it needs to be manually set to _OLD on wmf-config before merging this patch. Since we're already working with the database schema, this add a new, currently unused column for the creation data, so that T242847 will not require a new schema change. Bug: T242031 Bug: T242847 Change-Id: I6aa69c089340434737b55201b80398708a70c355		2023-02-24 15:33:00 +02:00
..
patch-add_generic_fields.sql	Make SQLite compatible patches	2020-10-04 20:40:27 +00:00
patch-remove_module_specific_fields.sql	Make SQLite compatible patches	2020-10-04 20:40:27 +00:00
tables-generated.sql	Database-level support for multiple auth devices	2023-02-24 15:33:00 +02:00