Skip to content

State the processing guarantee and expose the idempotency key - #31

Merged
thomasdarimont merged 1 commit into
mainfrom
gh-28-doc-processing-guarantees
Oct 5, 2026
Merged

thomasdarimont merged 1 commit into
mainfrom
gh-28-doc-processing-guarantees

Conversation

@thomasdarimont

Copy link
Copy Markdown
Collaborator

A SET is handled at least once, not exactly once: the javadoc of the handler and the dedup stores and both READMEs say so now, and SsfEventToken.idempotencyKey() (issuer and jti, also the dedup key) gives handlers the key for their own side effects. The SCIM-to-OIDC attribute mapping is documented as a deployment decision.

Closes #28

A SET is handled at least once, not exactly once: the javadoc of the
handler and the dedup stores and both READMEs say so now, and
SsfEventToken.idempotencyKey() (issuer and jti, also the dedup key)
gives handlers the key for their own side effects. The SCIM-to-OIDC
attribute mapping is documented as a deployment decision.

Closes #28

Signed-off-by: Thomas Darimont <thomas.darimont@googlemail.com>
@thomasdarimont
thomasdarimont merged commit e7d7493 into main Oct 5, 2026
10 checks passed
@thomasdarimont
thomasdarimont deleted the gh-28-doc-processing-guarantees branch October 5, 2026 22:56
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.

State the processing guarantee and expose the idempotency key

1 participant