Page MenuHomePhabricator

[identity] Better handle new flow users in v1 logout
ClosedPublic

Authored by bartek on Feb 18 2025, 1:51 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 1, 6:26 PM
Unknown Object (File)
Sat, Mar 29, 8:05 PM
Unknown Object (File)
Sat, Mar 29, 10:52 AM
Unknown Object (File)
Mon, Mar 24, 12:58 PM
Unknown Object (File)
Mon, Mar 24, 6:01 AM
Unknown Object (File)
Mon, Mar 24, 1:34 AM
Unknown Object (File)
Sun, Mar 23, 5:12 PM
Unknown Object (File)
Mon, Mar 17, 9:45 PM
Subscribers

Details

Summary

Addresses 1 and 2a from ENG-10202.

  • For v2 flow primary device logout, display an error message
  • For v1 flow primary device logout, remove backup to future-proof restore flow (make sure it falls back to v1).
Test Plan

Tested on staging

Diff Detail

Repository
rCOMM Comm
Branch
barthap/dev
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.

Add backup service url to commtest config

bartek published this revision for review.Feb 18 2025, 6:44 AM
bartek added inline comments.
services/identity/src/grpc_services/authenticated.rs
398–401

This can trigger alarms. Wondering if should lower it to warn.

kamil added inline comments.
services/identity/src/grpc_services/authenticated.rs
398–401

I would leave it as it is - we can lower if needed

1291

should we reuse to reduce code duplication, e.g. verify_device_on_device_list?

This revision is now accepted and ready to land.Feb 19 2025, 2:34 AM
services/identity/src/grpc_services/authenticated.rs
1291

Yes, good find

Use get_current_device_list helper in other places