Add FAQ entry on authentication-layer revocation - #583
Open
ivanauth wants to merge 1 commit into
Open
Conversation
When SpiceDB is composed with a separate authentication layer such as an OAuth 2.0 provider, revoking a credential at that layer does not affect SpiceDB permission checks, since the granting relationships are unchanged. Operators composing the two layers can wrongly assume otherwise, so document the boundary and point at relationship deletion, expiration, and caveats for revoking access in SpiceDB itself. Signed-off-by: ivanauth <ivan@authzed.com>
Contributor
|
Preview deployment skipped — @ivanauth does not have write access to this repository. A maintainer can trigger a preview deployment by re-running this workflow. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses authzed/spicedb#3279.
The docs never state the authentication/authorization boundary, so operators
composing SpiceDB with an OAuth 2.0 layer can assume that revoking a token
turns off downstream access. It doesn't: a check is computed from stored
relationships and caveat context, and never consults external credential state.