Skip to content

fix(routes): throttle the public SMS-sending routes per address - #393

Merged
roncodes merged 1 commit into
release/v0.6.72from
feature/sms-guard
Oct 13, 2026
Merged

roncodes merged 1 commit into
release/v0.6.72from
feature/sms-guard

Conversation

@roncodes

Copy link
Copy Markdown
Member

What

Driver and customer login-with-sms, forgot-password and request-creation-code get a throttle:5,1,fleetops-sms bucket per address on top of the API credential throttle.

This is an extra layer only. The spend bound for these endpoints comes from the SMS guard in core (fleetbase/core-api feature/sms-guard), which every send already passes through via SmsService; nothing in FleetOps needs to change for that.

Follow-ups (not in this PR)

  • CustomerController::requestCreationCode persists a stub User before the identity is verified; that should go.
  • Hashed single-use codes for driver and customer login/reset.

Tests

Route-only change; the route recorders in the existing tests accept chained middleware. Not run locally; CI verifies.

Driver and customer login-with-sms, forgot-password and request-creation-code
get a 5-a-minute bucket per address on top of the API credential throttle. An
extra layer only: core's SmsGuard budgets bound the spend when an attacker has
many addresses.
@roncodes
roncodes merged commit 661a335 into release/v0.6.72 Oct 13, 2026
4 of 6 checks passed
@roncodes
roncodes deleted the feature/sms-guard branch October 13, 2026 10:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant