docs: note serialized decision behavior for approval actions

Clarify that approve/reject/cancel decisions for a single approval request should be treated as serialized and not submitted in parallel.
2026-02-26 13:16:32 +00:00
parent 8bb3c1ce12
commit 464524da27
2 changed files with 2 additions and 0 deletions
@@ -139,6 +139,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`.
 - 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.
 - 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.
 - Never place client secrets, refresh tokens, or access tokens in URL query strings.
 - For OIDC providers, include a per-request `nonce` in authorisation requests.
 - For direct Cryptbin API usage, send `key_b64url` on unwrap calls; provider rejects key-mismatch unwrap attempts with `403 Forbidden`.