Open lmm-git opened 5 months ago
I think the current behavior is a sensible default for most use cases. For special use cases, I'd suggest fetching the openid-configuration
manually (since it's a simple HTTP GET request) and then using serde_json
to deserialize the ProviderMetadata
from the response.
Currently, when discovering a Provider, both
openid-configuration
andJWKS
get fetched.I have a specific use case where I do not need the JWKs, so I propose to decouple fetching JWKs and the default configuration to save one round trip and traffic.
For me, it would make sense to implicitly load the keys when requesting them from the provider object, but this would probably require some caching like discussed in #25