Add federated authorization tutorial#576
Open
sohanmaheshwar wants to merge 1 commit into
Open
Conversation
Adds a tutorial showing how to federate authorization across multiple identity providers (Keycloak OIDC + GitHub OAuth) by binding each external account to a canonical internal SpiceDB user. Includes the architecture diagram and links to the runnable demo in authzed/examples. Signed-off-by: Sohan Maheshwar <1119120+sohanmaheshwar@users.noreply.github.com>
Contributor
|
Preview deployment status for this pull request.
|
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.
What
Adds a new tutorial: Federate Authorization Across Multiple Identity Providers (
spicedb/tutorials/federated-authorization).It walks through using SpiceDB to centralize permissions when users authenticate through different identity providers (Keycloak OIDC + GitHub OAuth): each external account (
keycloak_account,github_account) binds to a canonical internaluser, and documents reference only thatuser— so the authorization model is unaffected by which IdP a user came from.Contents
*_account → bound_to → userbinding patternzedand Python examples for grant / check / share / lookupZedToken/at_least_as_fresh)authzed/examples/federated-authorizationAdded to the Tutorials nav via
app/spicedb/tutorials/_meta.ts.Note
The link to
authzed/examples/federated-authorizationresolves once authzed/examples#48 merges.