Page MenuHomePhabricator

[identity] Store social proof as a Map in DDB
ClosedPublic

Authored by bartek on Thu, Apr 4, 4:24 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Apr 27, 3:05 PM
Unknown Object (File)
Sat, Apr 27, 11:09 AM
Unknown Object (File)
Mon, Apr 22, 6:11 PM
Unknown Object (File)
Sun, Apr 21, 9:46 PM
Unknown Object (File)
Wed, Apr 17, 2:27 AM
Unknown Object (File)
Thu, Apr 11, 12:31 AM
Unknown Object (File)
Thu, Apr 11, 12:10 AM
Unknown Object (File)
Wed, Apr 10, 1:45 PM
Subscribers

Details

Summary

Instead of JSON-serializing and deserializing social proof, we can store it directly as a map attribute in DDB.

NOTE: Note this is breaking change - previous users with String social proof in DDB will fail. I found only 3 wallet users on staging and none on prod. I prefer manually migrating (or deleting) these 3 rows instead of keeping this code backwards compatible

Depends on D11547

Test Plan
  • Added unit test
  • Registered a wallet user and called FindUserIdentity to make sure that social proof is retrieved

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.Thu, Apr 4, 5:11 AM
varun added inline comments.
services/identity/src/siwe.rs
151 ↗(On Diff #38765)

nit: maybe this should be named something else instead of deserialized, like social_proof_from_attr

This revision is now accepted and ready to land.Thu, Apr 4, 8:22 PM