Skip to content

docs: add multi-tenant authorization cookbook #5015

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

Closed
benpsnyder wants to merge 1 commit into from
+493 −0
Closed

docs: add multi-tenant authorization cookbook #5015

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/docs/00200-core-concepts/00500-authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,11 @@ To authenticate your services, you have e few options depending on your OIDC pro
special user accounts designed for non-human users (e.g., servers, APIs). You
can create a service account and use its credentials to obtain an access token.

For multi-tenant SaaS authorization patterns that combine JWT claims, private
tables, reducers, views, roles, impersonation, API-key grants, and audit logs,
see
[Multi-Tenant Authorization Cookbook](./00500-authentication/00490-multi-tenant-authorization-cookbook.md).

## Authorization in your module

Obtaining an OIDC token is just the first step in securing your SpacetimeDB
Expand Down
Loading