Page MenuHomePhabricator

[web] Include `primaryIdentityPublicKey` in SIWE message
ClosedPublic

Authored by atul on Jan 26 2023, 4:34 PM.
Tags
None
Referenced Files
F3495807: D6410.id21406.diff
Thu, Dec 19, 10:03 AM
F3495801: D6410.id21479.diff
Thu, Dec 19, 10:00 AM
F3494863: D6410.diff
Thu, Dec 19, 7:02 AM
Unknown Object (File)
Nov 10 2024, 5:42 AM
Unknown Object (File)
Nov 9 2024, 5:06 PM
Unknown Object (File)
Nov 9 2024, 5:04 PM
Unknown Object (File)
Nov 7 2024, 7:45 AM
Unknown Object (File)
Nov 7 2024, 7:29 AM
Subscribers
None

Details

Summary

Include primaryIdentityPublicKey from olm in the SIWE message as we do on native. Note that this diff just includes getting the primaryIdentityPublicKey from olm and including it to the SIWE message statement.

NOTE: Persistence of the primaryIdentityPublicKey will happen in a subsequent diff.
Test Plan

Works as expected, can see that the primaryIdentityPublicKey is included in the SIWE message and everything is validated on the keyserver side!

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

atul edited the summary of this revision. (Show Details)
atul published this revision for review.Jan 26 2023, 4:40 PM
atul added inline comments.
web/account/siwe.react.js
86โ€“94 โ†—(On Diff #21405)

Why aren't we checking if the user intends to go through the SIWE flow or not like we do with siweNonce???

The plan is to include the primaryIdentityPublicKey for both "traditional" and SIWE log in requests in the future, so just making it available now (very minimal overhead).

remove <p> used for testing/debugging

This revision is now accepted and ready to land.Jan 26 2023, 5:46 PM
This revision was landed with ongoing or failed builds.Jan 27 2023, 12:49 PM
This revision was automatically updated to reflect the committed changes.