-
Notifications
You must be signed in to change notification settings - Fork 280
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.
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
chore(backend,types): Prevent system permissions usage in server-side #4816
Open
LauraBeatris
wants to merge
4
commits into
main
Choose a base branch
from
laura/orgs-441-do-not-allow-passing-system-permissions-to-has-from-the
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
--- | ||
'@clerk/backend': patch | ||
'@clerk/types': patch | ||
--- | ||
|
||
Add type-level validation to prevent server-side usage of system permissions | ||
|
||
System permissions (e.g., `org:sys_domains:manage`) are intentionally excluded from session claims to maintain reasonable JWT sizes. For more information, refer to our docs: https://clerk.com/docs/organizations/roles-permissions#system-permissions |
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -15,6 +15,7 @@ import type { | |
OrganizationCustomPermissionKey, | ||
OrganizationCustomRoleKey, | ||
OrganizationPermissionKey, | ||
OrganizationSystemPermissionPrefix, | ||
} from './organizationMembership'; | ||
import type { ClerkResource } from './resource'; | ||
import type { | ||
|
@@ -25,6 +26,29 @@ import type { | |
import type { TokenResource } from './token'; | ||
import type { UserResource } from './user'; | ||
|
||
type DisallowSystemPermissions<P extends string> = P extends `${OrganizationSystemPermissionPrefix}${string}` | ||
? 'System permissions are not included in session claims and cannot be used on the server-side' | ||
: P; | ||
Comment on lines
+29
to
+31
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is really cool! |
||
|
||
/** | ||
* Type guard for server-side authorization checks using session claims. | ||
* System permissions are not allowed since they are not included | ||
* in session claims and cannot be verified on the server side. | ||
*/ | ||
export type CheckAuthorizationFromSessionClaims = <P extends OrganizationCustomPermissionKey>( | ||
isAuthorizedParams: WithReverification< | ||
| { | ||
role: OrganizationCustomRoleKey; | ||
permission?: never; | ||
} | ||
| { | ||
role?: never; | ||
permission: DisallowSystemPermissions<P>; | ||
} | ||
| { role?: never; permission?: never } | ||
>, | ||
) => boolean; | ||
|
||
export type CheckAuthorizationFn<Params> = (isAuthorizedParams: Params) => boolean; | ||
|
||
export type CheckAuthorizationWithCustomPermissions = | ||
|
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you think we should add a test case for
useAuth()
where the type says that sys permissions are allowed ?In order to not break something in the future