Clears the Redis policy cache and invalidates local caches in ALL Core-API instances.
Propagation Mechanism:
- Deletes policy keys from Redis (L2 shared cache)
- Publishes Redis Pub/Sub event to "policy-cache-updates" channel
- All Core-API instances receive event and invalidate their L1 caches (Caffeine)
- Next cryptographic operation will reload fresh policies from Redis or database
Behavior:
• Without tenantId parameter: Clears entire policy cache (all tenants + deployment)
• With tenantId parameter: Clears only that specific tenant's policies
Use Cases:
• Emergency cache invalidation across entire cluster
• Policies updated directly in database (bypassing Admin API)
• Cache corruption suspected
• Testing policy changes in production
• Troubleshooting policy inconsistencies
• Forcing immediate policy refresh cluster-wide
Performance Impact:
• Propagation latency: ~10-15ms via Redis Pub/Sub
• Next operations will experience cache miss (slower initial request)
• Automatic cache repopulation on demand
Note: This operation only clears cache. To reload policies from database,
use the POST /sync endpoint after clearing cache.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
204Cache cleared successfully (no content returned)
406Not Acceptable — the request Accept header excludes every representation this endpoint produces. Per RFC 9110 §15.5.7 the response carries NO body and NO Content-Type.