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.
feat(edges): createEdge template + auth hardening F1/F2 #217
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
Uh oh!
There was an error while loading. Please reload this page.
feat(edges): createEdge template + auth hardening F1/F2 #217
Changes from all commits
af6774cFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
For browser calls to
categories-api(for examplesrc/hooks/useProductsByCategory.tsusessupabase.functions.invoke), the browser sends an unauthenticatedOPTIONSpreflight before the real request. Because this JWT check runs before theOPTIONSbranch below, the preflight gets a 401 instead of a 2xx CORS response, so the browser blocks the actual authenticated category request.Useful? React with 👍 / 👎.
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.
The new guards are commented as allowing “agente ou acima”, but
requireRole(authCtx, "agente")only accepts a literalagenterole (besidesdev);supervisor/legacyadminonly pass when the required role issupervisororadmin. A supervisor who does not also have anagenterow will now get 403 on these newly protected frontend flows, including comparison AI, even though the intended hierarchy says supervisors are above agents.Useful? React with 👍 / 👎.
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.
For browser calls to
dropbox-list(documented insrc/hooks/useDropboxFiles.ts), the unauthenticatedOPTIONSpreflight reaches this JWT guard before the handler'sOPTIONSresponse below. That makes the preflight return 401, so the browser blocks the real authenticated Dropbox list/check request even when the user has a valid session.Useful? React with 👍 / 👎.
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.
Once
CRON_SECRETis configured, this guard only acceptsx-cron-secret, but the admin page still invokesownership-auditfrom the browser with a normal Supabase JWT (src/pages/admin/OwnershipAuditAdminPage.tsx). That means the “run now” action for admins/devs will start returning 401 even though this function is documented as cron-or-manual and the underlying RPC checks admin permissions.Useful? React with 👍 / 👎.
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.
When
CRON_SECRETis configured as the post-merge action requires, this newauthorizeCroncheck only accepts thex-cron-secretheader. I checkedsupabase/cron/cron-config.sql, and the existing scheduled callers forprocess-queue,send-digest, andcleanup-notificationsstill send onlyAuthorization: Bearer <service_role>plusContent-Type, so those jobs will start receiving 401s and stop processing queues/digests/cleanup unless the cron definitions are updated or service-role bearer is still accepted.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.