Page MenuHomePhabricator

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

Authored by bartek on Apr 4 2024, 4:24 AM.
Tags
None
Referenced Files
F3529121: D11548.diff
Tue, Dec 24, 3:32 PM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Sun, Dec 22, 4:32 AM
Unknown Object (File)
Nov 18 2024, 5:36 AM
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.Apr 4 2024, 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.Apr 4 2024, 8:22 PM