You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`redis_unavailable`|`failure` / `degraded`| none | Redis unavailable for authentication or throttling. |
44
44
|`login_success`|`success`| user email | User completed TOTP login. |
45
-
|`login_failure`|`failure`| user email, when known | Login failed. TOTP code is never logged. |
45
+
|`login_failure`|`failure`| user email, when known | Login failed. TOTP code is never logged. Invalid-code failures include a short-window failed-attempt count for audit context, but accounts are not hard-locked by that counter. |
46
46
|`setup_complete`|`success`| user email | Invitation-based TOTP setup completed. |
47
47
|`setup_failure`|`failure`| user email | TOTP setup verification failed. |
48
48
|`admin_user_invited`|`success`| admin email | Admin created an invitation. |
Copy file name to clipboardExpand all lines: docs/guides/developer-reference.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,7 +220,8 @@ For production portal deployments:
220
220
- The legacy `RESULT_SERVER_KEY` variable is still accepted as runner `default` for compatibility, but should be rotated to `RESULT_SERVER_KEYS`.
221
221
- See `docs/deploy/key-management.md` for generation and rotation guidance.
222
222
-`REDIS_URL` must point to a monitored Redis instance; production authentication refuses login when Redis is unavailable.
223
-
- API ingest and query endpoints use Redis-backed rate limits by default; set `RESULT_SERVER_MAX_UPLOAD_MB` and `RESULT_SERVER_MAX_ARCHIVE_MEMBER_MB` when deployment-specific upload limits are needed.
223
+
- Login verification, API ingest/query, and admin write endpoints use Redis-backed rate limits by default; set `RESULT_SERVER_MAX_UPLOAD_MB` and `RESULT_SERVER_MAX_ARCHIVE_MEMBER_MB` when deployment-specific upload limits are needed.
224
+
- Repeated login failures are tracked per email for audit context only; source-scoped Redis rate limits enforce login traffic control without hard-locking a target account.
224
225
- Admin-managed affiliations are only rejected when they contain unsafe path/control characters or the comma delimiter used by the form; set `RESULT_SERVER_ALLOWED_AFFILIATIONS` only when a deployment wants to enforce a fixed comma-separated allowlist.
225
226
- Security-relevant auth, API, and admin actions emit structured `benchkit.audit` events; see `docs/cx/AUDIT_LOG_SPEC.md`.
226
227
-`app_dev.py` is localhost-only, uses ephemeral development secrets when none are provided, and enables the Werkzeug debugger only with `RESULT_SERVER_DEV_DEBUG=1`.
0 commit comments