Page MenuHomePhabricator

[identity] Add verification for replacing a device
ClosedPublic

Authored by bartek on Apr 22 2024, 6:46 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 3, 5:47 AM
Unknown Object (File)
Oct 12 2024, 4:16 PM
Unknown Object (File)
Oct 12 2024, 4:16 PM
Unknown Object (File)
Oct 12 2024, 4:16 PM
Unknown Object (File)
Oct 12 2024, 4:15 PM
Unknown Object (File)
Oct 10 2024, 6:56 AM
Unknown Object (File)
Aug 29 2024, 7:12 PM
Unknown Object (File)
Aug 8 2024, 10:51 AM
Subscribers

Details

Summary

Added possibility to replace a device in device list

Depends on D11687

Test Plan
  • Added unit tests
  • Called UpdateDeviceList RPC with payload that replaced exactly one device - pass
  • Called UpdateDeviceList RPC with payload that tried to replace primary device - fail

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Apr 23 2024, 11:59 PM
varun added inline comments.
services/identity/src/device_list.rs
106 ↗(On Diff #39343)
127 ↗(On Diff #39343)

don't we need to make sure that the previous and new device in the replacement are both keyservers?

This revision is now accepted and ready to land.Apr 25 2024, 10:09 PM
services/identity/src/device_list.rs
127 ↗(On Diff #39343)

Yeah this comment is a bit misleading. These validation functions are device-type-agnostic. Generally the logic is going to be extended when we add support for keyserver QR login