Page MenuHomePhabricator

[landing] Include `Device IdPubKey` in SIWE message statement
ClosedPublic

Authored by atul on Dec 31 2022, 3:42 AM.
Tags
None
Referenced Files
F3892773: D6132.diff
Sat, Jan 25, 12:21 AM
Unknown Object (File)
Thu, Jan 23, 8:09 AM
Unknown Object (File)
Tue, Jan 21, 2:08 PM
Unknown Object (File)
Tue, Jan 21, 4:45 AM
Unknown Object (File)
Sat, Jan 18, 8:52 PM
Unknown Object (File)
Sun, Jan 12, 7:25 AM
Unknown Object (File)
Fri, Jan 10, 9:19 AM
Unknown Object (File)
Fri, Jan 10, 8:38 AM
Subscribers
None

Details

Summary

If public key passed as header (siwePrimaryIdentityPublicKey), we'll include it in the SIWE message statement.

For the timebeing if a siwePrimaryIdentityPublicKey is NOT being passed in as header, we'll fallback to the previous SIWE message statement without the public key. Will go back and enforce existence of siwePrimaryIdentityPublicKey (with necessary error handling, error messages, etc) later in the stack.


Depends on D6131

Test Plan

The Device IdPubKey is being included in SIWE message statement:

IMG_FD3B200D6742-1.jpeg (2×1 px, 482 KB)

Diff Detail

Repository
rCOMM Comm
Branch
master
Lint
No Lint Coverage
Unit
No Test Coverage