Add API auth with sessions; remove legacy code - #398
Merged
Conversation
Introduce a new authentication system for the API: add auth routes, types, session cookie helpers, JWT signing/verification, password hashing, and session middleware (apps/api/src/auth/*). Update README with JWT_SECRET and CORS_ORIGIN and document auth endpoints. Update apps/api/package.json to include runtime and dev deps needed for auth (bcryptjs, jsonwebtoken, cookie-parser and types) and remove the seed/test scripts. Remove a large set of legacy/unused modules and templates (legacy capsules routes/models, analytics, attachments, admin routes/middleware, seeding script, many tooling templates and docs) and add several web client pieces (auth-client, Nav, login/register components, DashboardGate) and i18n/message updates. This consolidates auth/session handling and prunes obsolete code in preparation for the new auth flow.
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.
Introduce a new authentication system for the API: add auth routes, types, session cookie helpers, JWT signing/verification, password hashing, and session middleware (apps/api/src/auth/*). Update README with JWT_SECRET and CORS_ORIGIN and document auth endpoints. Update apps/api/package.json to include runtime and dev deps needed for auth (bcryptjs, jsonwebtoken, cookie-parser and types) and remove the seed/test scripts. Remove a large set of legacy/unused modules and templates (legacy capsules routes/models, analytics, attachments, admin routes/middleware, seeding script, many tooling templates and docs) and add several web client pieces (auth-client, Nav, login/register components, DashboardGate) and i18n/message updates. This consolidates auth/session handling and prunes obsolete code in preparation for the new auth flow.