Possibility to apply retry mechanism when trying to fetch JWK keys on ReactiveRemoteJWKSource

Expected Behavior

While using NimbusReactiveJwtDecoder/ReactiveRemoteJWKSource
There should be a way to configure a retry mechanism during the process of fetching the JWK info, so in case the provider of the JWK is temporarily unavailable, it could reduce the chance of facing an exception

Current Behavior

While using NimbusReactiveJwtDecoder/ReactiveRemoteJWKSource in case the provider of the JWK info is temporarily unavailable there no retry in place (also not a way to configure it), so the application logic just breaks as this information is required for further processing

Context

• we have another service which contains the JWK information
• this service may have some issues, which implies on a short downtime
• while the service is down, we faced this issue (JWK could not be fetched and the exception was propagated)
• one idea would be to make it possible to configure timeout for the JWT fetching logic (I can work on it in case you believe it could be a good option, but I am also fine to work on another idea)

Start with NimbusReactiveJwtDecoder and ReactiveRemoteJWKSource, then trace how JWK fetching failures are propagated. Define the retry or timeout configuration needed for temporary provider outages, and verify that applications can use it without immediately receiving the fetch exception.