Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single user area group key rotation #6975

Merged
merged 6 commits into from
Jun 5, 2024

Conversation

vitoreiji
Copy link
Contributor

tutadb#1770

@vitoreiji vitoreiji force-pushed the 1770-user-area-group-key-rotation branch 3 times, most recently from cabc684 to 8a5e464 Compare May 29, 2024 14:22
@vitoreiji vitoreiji force-pushed the 1770-user-area-group-key-rotation branch 5 times, most recently from b131b28 to b90d89c Compare June 4, 2024 13:09
…group key updates using a distribution key.

tutadb#1795
@vitoreiji vitoreiji force-pushed the 1770-user-area-group-key-rotation branch from b90d89c to e92ef15 Compare June 4, 2024 14:03
@vitoreiji vitoreiji force-pushed the 1770-user-area-group-key-rotation branch from e92ef15 to 1125605 Compare June 4, 2024 15:00
sarashub and others added 4 commits June 5, 2024 09:59
When loading a key at a certain version, if we notice the user has a key for that group with a lower version, this must mean that the memberships are out-of-date, because they should always have the latest key versions.

When this happens, we force downloading the user and update it on the facade, then we try getting the key again.

tutadb#1770
@vitoreiji vitoreiji force-pushed the 1770-user-area-group-key-rotation branch from 1125605 to 8a18979 Compare June 5, 2024 08:00
@vitoreiji vitoreiji merged commit 8a18979 into master Jun 5, 2024
1 check passed
@vitoreiji vitoreiji deleted the 1770-user-area-group-key-rotation branch June 5, 2024 09:31
@vitoreiji vitoreiji added this to the 232.240606.0 milestone Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants