docs: note cryptbin credential-binding requirements

Document that new cryptbin items can enforce creating-credential binding for unwrap/update/delete operations in addition to key proof.
This commit is contained in:
Andy Dixon
2026-02-26 13:25:20 +00:00
parent 62544d86b4
commit 32208c7701
2 changed files with 2 additions and 0 deletions
+1
View File
@@ -145,6 +145,7 @@ This wrapper now delegates to `BlackWall\Auth\AuthClient`.
- 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`.
- For newly created Cryptbin items, continue using the creating WebAuthn credential for unwrap/update/delete flows.
- Always use HTTPS in production.
- Store refresh tokens securely.
- Keep access tokens out of logs and browser-visible output.