[TT-15683] Add JWKS cache flush to the Dashboard API and MDCB #7523
probelabs / Visor: dependency
succeeded
Nov 14, 2025 in 3m 57s
✅ Check Passed (Warnings Found)
dependency check passed. Found 1 warning, but fail_if condition was not met.
Details
📊 Summary
- Total Issues: 1
- Warning Issues: 1
Issues by Category
Architecture (1)
⚠️ gateway/redis_signals.go:44 - This change introduces a new Redis notification command,NoticeInvalidateJWKSCacheForAPI, which the gateway is now configured to consume. For this feature to be fully functional in a Multi-Data Center Bridge (MDCB) environment, a corresponding change is required in the publisher component (Tyk Dashboard, using tyk-sink) to send this command. Without the publisher-side implementation, this new cache-flushing capability will not be triggerable via MDCB.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check warning on line 44 in gateway/redis_signals.go
probelabs / Visor: dependency
architecture Issue
This change introduces a new Redis notification command, `NoticeInvalidateJWKSCacheForAPI`, which the gateway is now configured to consume. For this feature to be fully functional in a Multi-Data Center Bridge (MDCB) environment, a corresponding change is required in the publisher component (Tyk Dashboard, using tyk-sink) to send this command. Without the publisher-side implementation, this new cache-flushing capability will not be triggerable via MDCB.
Raw output
Ensure a corresponding ticket and pull request exist for the Tyk Dashboard/tyk-sink to implement the publishing of the `NoticeInvalidateJWKSCacheForAPI` command to complete the end-to-end feature.
Loading