docs: require non-URL handling for enrollment links

Clarify that enrollment URLs are sensitive bearer material and must not be transported in redirect query strings or logs.
2026-02-26 12:40:33 +00:00
parent fb60a1eccb
commit 6cc2ddabd0
2 changed files with 2 additions and 0 deletions
@@ -154,6 +154,7 @@ Provider user/project assignment views may exclude disabled projects even if his
 - If you call provider WebAuthn login challenge/verify endpoints directly, use `POST` only.
 - Treat admin enrollment URL export as a state-changing operation: call it with `POST` and include a valid CSRF token.
 - 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.
 - Configure OAuth client redirect URIs as HTTPS in production; reserve HTTP for localhost loopback testing only.
 - Assume provider rate limits are enforced per source identity (for example IP) and shared across related auth endpoints.
 - Treat report/export-style provider endpoints as high-cost and expect stricter rate limits.