Page MenuHomePhabricator

[web] Ensure that `[primary/notification]IdentityPublicKeys` are set in `TraditionalLoginForm`
ClosedPublic

Authored by atul on Feb 23 2023, 9:18 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 2:11 PM
Unknown Object (File)
Wed, Dec 18, 10:13 AM
Unknown Object (File)
Tue, Dec 17, 9:02 AM
Unknown Object (File)
Fri, Dec 6, 12:27 AM
Unknown Object (File)
Thu, Nov 28, 1:00 PM
Unknown Object (File)
Tue, Nov 26, 3:36 PM
Unknown Object (File)
Nov 22 2024, 11:08 AM
Unknown Object (File)
Nov 22 2024, 10:28 AM
Subscribers
None

Details

Summary

Ensure that primaryIdentityPublicKeys and notificationIdentityPublicKeys are set before enabling TraditionalLoginForm. Also pass both keypairs to user-actions:logIn(...), but pull them out from restLogInInfo to ensure we don't break keyserver request input validation.


Depends on D6880

Test Plan

Still able to log in to account from both web and native.

Diff Detail

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

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Feb 23 2023, 9:25 PM
Harbormaster failed remote builds in B16866: Diff 23045!
atul requested review of this revision.Feb 23 2023, 10:04 PM

Accepting to unblock, but not clear why we're sending primaryIdentityPublicKey up twice

web/account/traditional-login-form.react.js
87

Why are we still passing this in?

This revision is now accepted and ready to land.Feb 24 2023, 8:17 AM
web/account/traditional-login-form.react.js
87

All the primaryIdentityPublicKey stuff gets ripped out in later diff. First want to get all the identity keys persisted in ServerDB and then will remove the olds stuff.