At the moment if we change the jwkSetUri on a client registration it continues to use the old value because we cache the validator based on the client ID. This isn't a problem if config changes require an application restart, but if the value can be changed at runtime it doesn't get picked up because the old validator is still in the cache.
At the moment if we change the jwkSetUri on a client registration it continues to use the old value because we cache the validator based on the client ID. This isn't a problem if config changes require an application restart, but if the value can be changed at runtime it doesn't get picked up because the old validator is still in the cache.