-
Bug
-
Resolution: Done
-
Major
-
7.4.0.GA
The current implementation of the cache inside the JwkManager just caches by the jwks url and it does take into account if a new kid is passed. This avoids the rotation of keys because the new key is not loaded until the current cache expires.
The idea is going to be always refreshing the jwks url if the kid is new. Just adding a new time option to avoid flooding of the endpoint (a minimum time in which consecutive requests are not allowed).
- incorporates
-
ELY-2194 JWK implementation in JwkManager does not work properly on key rotation
- Resolved
- is cloned by
-
JBEAP-22339 [GSS](7.3.z) ELY-2194 - JWK implementation in JwkManager does not work properly on key rotation
- Closed
- is incorporated by
-
JBEAP-22367 (7.4.z) Upgrade Elytron from 1.15.5.Final-redhat-00001 to 1.15.6.Final-redhat-00001
- Closed