feat: add capabilities column and JWT support#148
Open
jakebromberg wants to merge 1 commit intomainfrom
Open
Conversation
3 tasks
- Add capabilities text[] column to auth_user table - Include capabilities in JWT payload via definePayload - Register capabilities as Better Auth additionalField - Add unit tests for capability storage and JWT structure
jakebromberg
force-pushed
the
feature/capabilities
branch
from
e2f9a10 to
ba1258d
Compare
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.
Summary
Adds cross-cutting capabilities (e.g.,
editor,webmaster) to the auth system, independent of the role hierarchy.capabilitiestext[] column toauth_usertable (migration 0026)capabilitiesas a Better AuthadditionalFieldon the user schemacapabilitiesin JWT payload viadefinePayloadContext
Split out from #143, which mixed this work with email account-setup changes that have since been superseded by #145 and #147.
Part of a cross-repo rollout:
Test plan
npm run build