HOCO B2B
Team tasksAnis

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.

FieldDetails
Task codeSRV-52
PhaseP1 — V1 build & integration
Product scopeV1
StatusPlanned
StartMon 7 Dec 2026
DueTue 8 Dec 2026
ResponsibleAnis — Full-stack developer
Co-responsible—
Effort1 person-day(s) planned · 3 from scratch · size S
Area · appServer · server
Depends onSRV-51
UnblocksWEB-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

#SubtaskOwner
1auth.login accepts a reseller's confirmed email; password reset by that emailAnis
2Purpose EMAIL_CHANGE and the login email in me.updateAnis
3Purpose LOGIN and auth.loginCodeAnis
4Notification security.email_changedAnis

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

RequirementTitleRelease
AUTH-04Reseller sign-in (phone or email + password, or a one-time code) and password reset by OTPV1
AUTH-07Password policy, hashing, OTP expiry/resend cooldown and attempt limitingV1
AUTH-08Account statuses (pending validation, active, suspended, disabled) gate what each user can doV1

API surface

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.

On this page