Feature #10431
openFix Login/Logout Fallback and Resolve Frontend Build Issues
Subtasks
Related issues
Updated by Teja Sriram Sangani about 1 month ago
- Status changed from New to Resolved
- % Done changed from 0 to 90
- Fixed the login and logout fallback flow so users are redirected to the main FE login page when the Accounts service is unavailable, instead of seeing a connection-refused error.
- Updated session expiry and unauthorized (401) handling to follow the same fallback login flow, ensuring users can return to the login page even when the Accounts service is down.
- Resolved the slow login and ECONNRESET issue by reusing the existing MongoDB connection pool instead of creating a new database connection for every company login request.
- Improved the global login flow by making it email-first, removing leftover company selection data, and allowing activity-log failures to occur without blocking a successful login.
- Added clearer timeout and 503 error handling so database connection failures provide a proper response instead of leaving the login request hanging or failing with an unclear error.
- Resolved the merge conflict while keeping the required store picker and hero UI, ensuring catalogs still appear when store matching fails and preserving the required type and store parameters in detail URLs.
- Fixed the frontend production build issues by removing duplicate JSX/object entries and cleaning unused or invalid TypeScript code that was causing compilation failures.
- Successfully verified both frontend production builds after the fixes, unblocking the builds and completing the login, logout, merge conflict, and build-related work.