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.

Sign up for GitHub

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

Jump to bottom

Single user area group key rotation #6975

Merged
merged 6 commits into from
Jun 5, 2024
Merged

Single user area group key rotation #6975

merged 6 commits into from
Jun 5, 2024

Commits on Jun 4, 2024

  1. Extract keyCache from KeyLoaderFacade and UserFacade and handle user … 

    …group key updates using a distribution key.

tutadb#1795
    @vaf-hub @vitoreiji
    vaf-hub authored and vitoreiji committed Jun 4, 2024
    Configuration menu
    Copy the full SHA
    d348d4b View commit details
    Browse the repository at this point in the history

  2. Allow area groups to rotate keys 

    tutadb#1770
    @sarashub @vitoreiji
    sarashub authored and vitoreiji committed Jun 4, 2024
    Configuration menu
    Copy the full SHA
    0a77de9 View commit details
    Browse the repository at this point in the history

Commits on Jun 5, 2024

  1. Bypass cache when we know the group is out-of-date 

    tutadb#1770
    @sarashub @vitoreiji
    sarashub authored and vitoreiji committed Jun 5, 2024
    Configuration menu
    Copy the full SHA
    7f17ee8 View commit details
    Browse the repository at this point in the history

  2. Update user when the one we have is out-of-date 

    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 committed Jun 5, 2024
    Configuration menu
    Copy the full SHA
    f819a01 View commit details
    Browse the repository at this point in the history

  3. Clean up after review 

    tutadb#1770
    @vitoreiji
    vitoreiji committed Jun 5, 2024
    Configuration menu
    Copy the full SHA
    726cdfa View commit details
    Browse the repository at this point in the history

  4. Update to SystemModel101 

    tutadb#1770
    @vitoreiji
    vitoreiji committed Jun 5, 2024
    Configuration menu
    Copy the full SHA
    8a18979 View commit details
    Browse the repository at this point in the history