Repository navigation
feat: real Cognito authentication with owner/manager/counter_staff roles - #14
Merged
Merged
Conversation
Replaces the free-text ?shop_id=&counter_id= identity scheme with real sign-up/sign-in (Cognito User Pool), closing the cross-tenant gap crudTable.ts's own comments flagged (any shop_id was previously accepted from an unauthenticated client). Every REST route now sits behind a JWT authorizer; shop_id is derived from the verified token's claims, never trusted from the request. WebSocket $connect verifies the same token manually since API Gateway has no native WS JWT authorizer. Self-signup makes you the "owner" of a new shop; owners invite manager/counter_staff accounts via a new POST /staff admin endpoint (AdminCreateUser, scoped to the inviter's own shop_id). Catalog writes (products/categories/suppliers) are owner/manager-only; counter staff keep full checkout/transactions access. Frontend: AuthContext/cognito.ts drive sign-up, email confirmation, sign-in, and the forced-password-change flow for invited staff; App.tsx gates on auth status before showing the counter picker; StaffPage lets an owner invite staff and see role-gated nav. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
Replaces the free-text ?shop_id=&counter_id= identity scheme with real sign-up/sign-in (Cognito User Pool), closing the cross-tenant gap crudTable.ts's own comments flagged (any shop_id was previously accepted from an unauthenticated client). Every REST route now sits behind a JWT authorizer; shop_id is derived from the verified token's claims, never trusted from the request. WebSocket $connect verifies the same token manually since API Gateway has no native WS JWT authorizer.
Self-signup makes you the "owner" of a new shop; owners invite manager/counter_staff accounts via a new POST /staff admin endpoint (AdminCreateUser, scoped to the inviter's own shop_id). Catalog writes (products/categories/suppliers) are owner/manager-only; counter staff keep full checkout/transactions access.
Frontend: AuthContext/cognito.ts drive sign-up, email confirmation, sign-in, and the forced-password-change flow for invited staff; App.tsx gates on auth status before showing the counter picker; StaffPage lets an owner invite staff and see role-gated nav.