Page MenuHomePhabricator

[keyserver] Use keyserverID instead of userID when creating invite link blobs
ClosedPublic

Authored by tomek on Apr 22 2024, 4:49 AM.
Tags
None
Referenced Files
F5283030: D11708.diff
Mon, Apr 7, 9:46 AM
Unknown Object (File)
Feb 27 2025, 7:25 PM
Unknown Object (File)
Feb 27 2025, 7:25 PM
Unknown Object (File)
Feb 26 2025, 8:09 AM
Unknown Object (File)
Feb 26 2025, 8:00 AM
Unknown Object (File)
Feb 17 2025, 11:14 PM
Unknown Object (File)
Jan 20 2025, 2:23 AM
Unknown Object (File)
Jan 20 2025, 2:23 AM
Subscribers

Details

Summary

For each link we create a blob that contains a keyserver ID that is later used as a part of the override on the client side. In a single-keyserver world, this value should be equal to 256 because this is the ID a client uses as a keyserver ID. Instead of using the correct value, we were using the ID of a user, taken from Identity - so it was a multi-keyserver keyserver ID.

This issue wasn't affecting prod because the ID of the keyserver on prod Identity is equal to 256.

https://linear.app/comm/issue/ENG-7789/invite-links-in-single-keyserver-world-fail

Test Plan

Tested if creating a new link and accepting it works with both single- and multi-keyserver IDs. (testing multi-keyserver ID was performed by having a client with usingCommservicesAccessToken set to false, and a keyserver with usingIdentityCredentials set to true).

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable