From 62544d86b4ae629cd0415f79622d646e0a8689e0 Mon Sep 17 00:00:00 2001 From: Andy Dixon Date: Thu, 26 Feb 2026 13:23:29 +0000 Subject: [PATCH] docs: add CIDR trusted-proxy guidance Clarify trusted-proxy configuration can use explicit IP/CIDR entries and should remain narrowly scoped for abuse-control integrity. --- README.md | 1 + docs/INTEGRATION_GUIDE.md | 1 + 2 files changed, 2 insertions(+) diff --git a/README.md b/README.md index e468e05..fe9aea4 100644 --- a/README.md +++ b/README.md @@ -138,6 +138,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`. - Handle provider CSV exports with formula-injection safety in mind if opening them in spreadsheet applications. - Treat generated enrollment URLs as secrets and keep them out of URL query strings and request logs. - For reverse-proxy deployments, harden trusted proxy/IP forwarding configuration to prevent spoofed client IP headers. +- Prefer narrowly scoped trusted-proxy entries (explicit IPs/CIDR ranges) instead of broad network trust. - Keep client-side admin mutation retries idempotent; approval workflows can be lock-serialized and should not be assumed to execute twice. - Do not submit parallel approve/reject/cancel decisions for the same approval request ID. - Apply bounded CSV import sizes and row counts for admin bulk-user operations. diff --git a/docs/INTEGRATION_GUIDE.md b/docs/INTEGRATION_GUIDE.md index 98ca4d6..eb6d13d 100644 --- a/docs/INTEGRATION_GUIDE.md +++ b/docs/INTEGRATION_GUIDE.md @@ -157,6 +157,7 @@ Provider user/project assignment views may exclude disabled projects even if his - Treat provider CSV exports as untrusted input in spreadsheet tools; prefer importing into systems that neutralise formula cells. - Treat enrollment URLs as sensitive bearer material: do not place them in redirect query parameters, logs, or analytics tags; keep them in one-time server-side flash/session state. - If your deployment runs behind reverse proxies, ensure trusted-proxy configuration is strict so spoofed forwarding headers cannot bypass IP-based abuse controls. +- Trusted proxy allowlists may be expressed as explicit IPs or CIDR ranges; avoid broad ranges and keep proxy chains minimal. - For approval-driven admin mutations, assume provider-side execution is serialized per approval item; client retries should still be idempotent and bounded. - This serialization applies across approval actions (approve/reject/cancel), so clients should avoid parallel decision submissions for the same request ID. - For provider CSV-based user import operations, enforce strict file-size and row-count limits in automation tooling and surface clear operator errors on limit breaches.