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

Proper handling of incompatible zedtokens #1723

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Proper handling of incompatible zedtokens #1723

wants to merge 3 commits into from

Commits on Jul 12, 2024

  1. Export the unique, stable, ID from datastore

    @josephschorr
    josephschorr committed Jul 12, 2024
    Configuration menu
    Copy the full SHA
    73300fd View commit details
    Browse the repository at this point in the history

  2. Setup defined (and configurable) behavior if a ZedToken from 

    an older datastore is used

All ZedTokens are now minted with the datastore's unique ID included
in the ZedToken and that ID is checked when the ZedToken is decoded.

In scenarios where the datastore ID does not match, either an error is
raised (watch, at_exact_snapshot) or configurable behavior is used
(at_least_as_fresh)

Fixes authzed#1541
    @josephschorr
    josephschorr committed Jul 12, 2024
    Configuration menu
    Copy the full SHA
    f120b8d View commit details
    Browse the repository at this point in the history

  3. Change to only store a prefix of the datastore's unique ID in the zed… 

    …token

Results in smaller tokens but given that datastore IDs are generated, should still minimize the chances of a conflict
    @josephschorr
    josephschorr committed Jul 12, 2024
    Configuration menu
    Copy the full SHA
    d19b1f7 View commit details
    Browse the repository at this point in the history