SRV-52 — Reseller sign-in by email and by one-time code
Email and password for confirmed reseller emails, purposes EMAIL_CHANGE and LOGIN, auth.loginCode, and a security notice when the login email changes.
| Field | Details |
|---|---|
| Task code | SRV-52 |
| Phase | P1 — V1 build & integration |
| Product scope | V1 |
| Status | Planned |
| Start | Mon 7 Dec 2026 |
| Due | Tue 8 Dec 2026 |
| Responsible | Anis — Full-stack developer |
| Co-responsible | — |
| Effort | 1 person-day(s) planned · 3 from scratch · size S |
| Area · app | Server · server |
| Depends on | SRV-51 |
| Unblocks | WEB-23, MRA-23 |
| Milestones | — |
Summary
Email and password for confirmed reseller emails, purposes EMAIL_CHANGE and LOGIN, auth.loginCode, and a security notice when the login email changes.
Description
Decision D-65, asked by Anis on 9 Nov 2026, not yet accepted by HOCO. A login email needs a code sent to it and the current password. The sign-in code follows D-64: WhatsApp when it is on, SMS otherwise, so real sending needs the same providers.
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | auth.login accepts a reseller's confirmed email; password reset by that email | Anis |
| 2 | Purpose EMAIL_CHANGE and the login email in me.update | Anis |
| 3 | Purpose LOGIN and auth.loginCode | Anis |
| 4 | Notification security.email_changed | Anis |
Deliverables
- apps/server/src/modules/identity/procedures.ts
- apps/server/src/modules/identity/me-procedures.ts
- packages/contracts/src/schemas/auth.ts
Acceptance criteria
- A confirmed email and the password sign a reseller in; an unconfirmed address does not
- Confirming an email needs its code and the current password
- A LOGIN code opens a session and reveals nothing about unknown phones
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| AUTH-04 | Reseller sign-in (phone or email + password, or a one-time code) and password reset by OTP | V1 |
| AUTH-07 | Password policy, hashing, OTP expiry/resend cooldown and attempt limiting | V1 |
| AUTH-08 | Account statuses (pending validation, active, suspended, disabled) gate what each user can do | V1 |
API surface
| Endpoint group | Operations |
|---|---|
| Authentication & sessions | 14 |
| Me, devices, app config & reference data | 9 |
Test measures
- Integration tests of both sign-ins, the email change and the refusals
Risks
- Each code sign-in costs a message once a real provider is on
KPI
- Delivered by Tue 8 Dec 2026 within 1 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.
WEB-22 — Reseller web code screens for WhatsApp
Sign-up and password-reset code screens word themselves from the channel and offer the SMS option.
WEB-23 — Reseller web sign-in options and login email
The sign-in page takes a phone or an email and offers a code; the settings page confirms a login email.