Feature #6508
closedEpic #6491: Project Base Set Up & Authentication
Backend & frontend Code Base setup
Subtasks
Related issues
Updated by Pavan Kumar Murala 23 days ago
- Due date set to 01/07/2026
- % Done changed from 0 to 30
- Estimated time set to 15:00 h
Admin portal (admin.noxa.com) — used by SUPER_ADMIN, ADMIN, and CLIENT (store owners)
Storefront (clientname.noxa.com) — used by CUSTOMERS only.
Requirements
Use NestJS backend and MongoDB.
Authentication must be JWT-based with:
• Access token (short-lived)
• Refresh token (long-lived, persisted in DB, HTTP-only cookie)
Every JWT must include: userId, role, tenantId (tenantId is null for SUPER_ADMIN).
Passwords must be hashed (bcrypt).
Email must be unique within each user type.
Updated by Pavan Kumar Murala 21 days ago
- % Done changed from 30 to 100
On the frontend, I have implemented access token and refresh token authentication.
Both tokens are stored securely in localStorage after login.
When the access token expires, the application automatically calls the refresh token API, sends the refresh token, and receives a new access token and refresh token, which are then updated in storage.
If the refresh token is also expired or invalid, the user is automatically logged out to maintain application security.
Updated by Yalavarthi Thriveni 21 days ago
- Target version set to E-Com & Admin PanelCore Setup & Product Catalog Integration
Updated by Pavan Kumar Murala 21 days ago
- Due date changed from 01/07/2026 to 01/08/2026
Updated by Pavan Kumar Murala 21 days ago
- Due date changed from 01/08/2026 to 01/07/2026
- Start date changed from 01/06/2026 to 01/07/2026
Updated by Pavan Kumar Murala 21 days ago
- Tracker changed from User Story to Feature
- Status changed from New to Resolved
Updated by Yalavarthi Thriveni 19 days ago
- Start date changed from 01/07/2026 to 01/06/2026
Updated by Yalavarthi Thriveni 19 days ago
- Status changed from Resolved to Closed
yes frontend & backend set done for Admin panel & e-commerce application set up also done