Page MenuHomePhabricator

[web][native] Don't persist temporary keyservers
AbandonedPublic

Authored by inka on Dec 29 2023, 5:40 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jan 22, 2:19 AM
Unknown Object (File)
Jan 19 2025, 6:54 AM
Unknown Object (File)
Jan 13 2025, 3:19 PM
Unknown Object (File)
Jan 2 2025, 5:51 PM
Unknown Object (File)
Jan 2 2025, 5:51 PM
Unknown Object (File)
Jan 2 2025, 5:51 PM
Unknown Object (File)
Dec 29 2024, 5:22 PM
Unknown Object (File)
Dec 27 2024, 3:22 PM
Subscribers

Details

Reviewers
ginsu
michal
kamil
Summary

issue: ENG-6097
We don't want to persist temporarily connected keyservers

If VERSION or VERIFY_INVITE_LINK endpoints were called, we should somehow mark the keyserver as “temporarily” connected - keyserverConnectionHandler will not be attempting to log the user in to that keyserver, and this keyserver will not be persisted.

  1. It might be useful to use the same cookie that we got from the keyserver, in the next request
  2. But calling those endpoints doesn’t necessarily mean that the user wants to permanently connect (login) to this keyserver. The user might for example resign from accepting an invite link.
Test Plan

Added a keyserver with connectionIssue: 'temporarily_connected', closed the app, opened the app, checked that the keyserver is gone

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage