History: Security

Every change to this page, newest first. Expand an entry to see what changed.

← Security

1. 2 Oct 2026 · +4 −6 lines
   Show changes

   ⋯
     |---|---|---|
     | Create | Admin or Developer, on **Developers** | The full key is shown once. A new key is pinned to the **latest** dated API version. |
   - | Rotate | Admin or Developer | Replaces the secret, keeps label, scopes and **version pin**. The old secret stops working within **30 seconds** — there is no overlap. |
   - | Revoke | Admin or Developer | Final. New requests with the key are refused within **30 seconds** (creatives: at once). |
   + | Rotate | Admin or Developer | Replaces the secret, keeps label, scopes and **version pin**. The old secret is refused within about **1 second** on every Wandura server (always within 30 seconds) — there is no overlap. |
   + | Revoke | Admin or Developer | Final. New requests with the key are refused within about **1 second** (always within 30 seconds). |
     | Already-issued tickets | — | Keep playing until they expire (≤ 30 minutes). They cannot be recalled. |
     
   - > **Rolling out.** A revoked key, or the old secret of a rotated key, is refused within about **1 second** on every Wandura server (always within 30 seconds).
   - 
     **Rotate without downtime:** create a second key with the same scopes, deploy it, check traffic has moved (**Last used** on the old key stops changing), then revoke the old one. A new key is pinned to the latest dated version: if your key is pinned to an older one, send `Wandura-Version: <your date>` with the new key, or read `api.pinned_version` from `GET /config` with both keys before you switch. See [Migrating versions](../guides/migrating-versions.md).
     
   - > **Rolling out.** Wandura receives an alert, in a private channel, when a playback key is created or rotated in your organisation and when your organisation reaches its playback limit. You still own your keys: Wandura does not watch them for misuse in real time.
   + Wandura monitors new and rotated playback keys and organisations that reach their playback limit. You still own your keys: watch **Last used** and **API usage**, and tell Wandura at once if you suspect a leak.
     
     Every key creation, rotation and revocation is recorded in Wandura's audit log with your organisation, the member who did it and the key prefix.
   ⋯
     ## If a key leaks {#leaked-key}
     
   - 1. **Revoke it** on **Developers** (any Admin or Developer). New requests stop within 30 seconds.
   + 1. **Revoke it** on **Developers** (any Admin or Developer). New requests stop within about a second.
     2. **Deploy a replacement** with the same scopes. Mind the version pin (above).
     3. **Tell Wandura** in your team's Wandura Discord channel: the key prefix, when and where it was exposed. Wandura can list the tickets issued with it (kept 90 days) and, if tickets already issued must stop before they expire, suspend the affected films for your organisation.
   ⋯

2. 2 Oct 2026 · Page created