Page MenuHomePhabricator

[identity] update change password RPCs to match whitepaper
ClosedPublic

Authored by varun on Tue, Jun 18, 9:41 AM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Jun 30, 5:20 AM
Unknown Object (File)
Sat, Jun 29, 8:30 PM
Unknown Object (File)
Fri, Jun 28, 8:33 AM
Unknown Object (File)
Fri, Jun 28, 12:37 AM
Unknown Object (File)
Thu, Jun 27, 4:34 PM
Unknown Object (File)
Thu, Jun 27, 11:20 AM
Unknown Object (File)
Thu, Jun 27, 1:16 AM
Unknown Object (File)
Tue, Jun 25, 5:05 PM
Subscribers

Details

Summary

per the whitepaper, we want clients to run Password-based Authentication before running Password-based Registration with the new password.

Test Plan

tested later in stack by calling the new RPCs from web and native

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

varun requested review of this revision.Tue, Jun 18, 9:58 AM
ashoat added inline comments.
native/schema/CommRustModuleSchema.js
88–94 ↗(On Diff #41455)

Does nothing currently call this?

shared/protos/identity_auth.proto
191–198 ↗(On Diff #41455)

Nit: I would move this above UpdateUserPasswordFinishRequest to properly reflect the order in which the messages are passed

use username as credential identifier

native/schema/CommRustModuleSchema.js
88–94 ↗(On Diff #41455)

yeah no callsites

shared/protos/identity_auth.proto
191–198 ↗(On Diff #41455)

sure will change this before landing

shared/protos/identity_auth.proto
191–198 ↗(On Diff #41455)

actually the order here determines the ordering in our gRPC-web codegen files. i'd rather not move everything around in those files

shared/protos/identity_auth.proto
191–198 ↗(On Diff #41455)

That's fair

You're doing OPAQUE login for old password and OPAQUE registration for new password in the same RPC. Smart!

This revision is now accepted and ready to land.Wed, Jun 19, 6:15 AM