gateway.auth.rateLimit 配置落地清单：先过 schema 再上线
用于修复 `gateway.auth.rateLimit` 被配置校验拒绝的问题：通过最小配置验证 + 重启回归，避免上线后鉴权限流失效。
GITHUBDiscovered 2026-02-14Author widingmarcus-cyber
Prerequisites
- You can edit gateway config and safely restart in a maintenance window.
- You have one test client to generate repeated auth requests.
Steps
- Apply a minimal `gateway.auth.rateLimit` patch in staging first and validate config parsing succeeds.
- Restart gateway and confirm startup logs show no validator/zod rejection for auth config.
- Send burst auth requests and verify throttling behavior matches configured thresholds.
- Promote same config to production only after staging pass and keep rollback config snapshot.
Commands
openclaw gateway config.getopenclaw gateway restartopenclaw gateway statusVerify
Gateway starts cleanly with rateLimit enabled, and repeated auth hits trigger predictable throttling instead of config failure.
Caveats
- Issue is recent and patch details may evolve quickly across minor releases（需验证）.
- Overly strict limits can lock out legitimate automation clients; tune gradually.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗