Page MenuHomePhabricator

[protos][identity] Add primary device keys to GetKeyserverKeys response
ClosedPublic

Authored by bartek on Mar 28 2024, 11:48 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Nov 29, 4:55 AM
Unknown Object (File)
Nov 3 2024, 11:41 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Unknown Object (File)
Oct 13 2024, 1:43 AM
Subscribers

Details

Summary

Addresses ENG-7161.

After discussions, we concluded that we need primary device public keys for social proof verification.
We can add it in a non-breaking manner to the existing RPC response.

Implemented function to fetch primary device data and added it to the RPC response.

Test Plan
  1. Registered user on mobile
  2. Set that user as a keyserver owner and registered the keyserver
  3. Called the RPC - returned keyserver keys, primary device's identity keys and username

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek published this revision for review.Mar 29 2024, 12:34 AM

Some comments/proposals appeared in ENG-7598 that we need to take into account here. Requesting review now to open discussions

Thanks for doing this! It makes sense to me. Agree with @varun's proposal in ENG-7598, and separately I think it would be good to address ENG-7532 soon to avoid breaking changes to this RPC (due to the use of Identity)

varun added inline comments.
services/identity/src/grpc_services/authenticated.rs
196

let's do this before we call get_keyserver_keys_for_user

This revision is now accepted and ready to land.Apr 1 2024, 9:14 PM

Find user identifier before getting keys