Page MenuHomePhabricator

[lib] Use identity service for keyserver session recovery
ClosedPublic

Authored by ashoat on Mar 31 2024, 7:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Nov 12, 10:41 AM
Unknown Object (File)
Tue, Nov 12, 8:09 AM
Unknown Object (File)
Tue, Nov 12, 6:55 AM
Unknown Object (File)
Tue, Nov 12, 2:58 AM
Unknown Object (File)
Tue, Nov 12, 1:09 AM
Unknown Object (File)
Mon, Nov 11, 9:43 PM
Unknown Object (File)
Mon, Nov 11, 7:23 PM
Unknown Object (File)
Wed, Nov 6, 10:13 PM
Subscribers
None

Details

Summary

This diff is gated on usingCommServicesAccessToken. We fall back to legacy keyserver auth if the new identity-based workflow doesn't work.

Depends on D11499

Test Plan

Tested in combination with later diffs:

  1. Set up multi-keyserver environment following Notion doc
  2. Test native keyserver recovery via keyserverAuth by deleting a cookie in MariaDB console
  3. Hardcode incorrect userID, try same test as 2, and confirm that it fails
  4. Test web keyserver recovery in the same way as in 2
  5. Test incorrect userID on web in the same way as in 3

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tomek added inline comments.
lib/components/keyserver-connection-handler.js
169–170 ↗(On Diff #38613)

Is there a reason to change the awaiting approach?

This revision is now accepted and ready to land.Apr 2 2024, 2:42 AM
lib/components/keyserver-connection-handler.js
169–170 ↗(On Diff #38613)

To be honest, I'm not sure. I wrote this code months ago, but it took a while to test it and feel confident putting the diffs up.

Looking at the redux-thunk docs, it seems like either approach should work.

Before landing, I'll do some testing and see if we can keep the previous approach.

Go back to awaiting dispatchActionPromise