Page MenuHomePhabricator

[services][identity] update user's public keys in ddb during PAKE login
ClosedPublic

Authored by varun on Sep 21 2022, 11:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Nov 18, 10:22 PM
Unknown Object (File)
Mon, Nov 18, 7:32 PM
Unknown Object (File)
Sat, Nov 9, 7:38 PM
Unknown Object (File)
Sat, Nov 9, 7:38 PM
Unknown Object (File)
Sat, Nov 9, 7:38 PM
Unknown Object (File)
Sat, Nov 9, 7:35 PM
Unknown Object (File)
Tue, Nov 5, 2:07 AM
Unknown Object (File)
Oct 9 2024, 8:45 PM

Details

Summary

If a user logs in, we should update the users table to reflect the potentially new deviceID-userPublicKey mapping.

We should refactor these service methods to not loop. Tracked here.

Depends on D5200

Test Plan

verified that PAKE login on a new device updates the devices map in dynamodb to reflect the new public key

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

remove unnecessary closure

services/identity/src/service.rs
604–609 ↗(On Diff #17008)

Feel like we got a lot going on here in a deeply nested fashion.
Not sure how i feel about having a nested await inside of the construction of a value.

services/identity/src/service.rs
604–609 ↗(On Diff #17008)

yeah that's true. i have a linear task (linked in summary) to refactor this whole thing anyway. will tackle then

This revision is now accepted and ready to land.Sep 23 2022, 6:02 AM