docs: add Better Auth integration guide#5009
Closed
benpsnyder wants to merge 3 commits into
Closed
Conversation
Contributor
|
Hi @benpsnyder, thanks for your contribution to the docs. We don't accept draft PRs in our repo to keep our PRs relatively neat and manageable, so I'm going to close this for now, at least until you have a complete PR for us to review. |
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
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.
Summary
Why
This is one focused documentation slice from #5004. Better Auth can work well with SpacetimeDB, but the safe integration depends on issuing a verifiable JWT with a stable issuer, subject, SpacetimeDB-specific audience, and JWKS-backed signing keys. Enterprise identity plugins such as SSO and SCIM should normalize identity and membership inside Better Auth; SpacetimeDB should receive only a short-lived, audience-scoped JWT after the app authorizes the actor.
The guide now also covers the broader enterprise-federation shape: Microsoft Entra ID, Google Workspace, Keycloak, Auth0, WorkOS-style hosted services, and custom OIDC/SAML providers should be treated as app-side adapters. SpacetimeDB should not need provider-specific integrations for each identity system.
Validation
git diff --checkpnpm --dir docs typecheckpnpm --dir docs buildThe docs build passes. It still prints the existing
docusaurus-plugin-llms-txtwarning for/docs/ask-ai/ask-ai, which is unrelated to this change.Refs #5004