Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple fetching of openid-configuration and JWKS #159

Open
lmm-git opened this issue Apr 15, 2024 · 1 comment
Open

Decouple fetching of openid-configuration and JWKS #159

lmm-git opened this issue Apr 15, 2024 · 1 comment

Comments

@lmm-git
Copy link

lmm-git commented Apr 15, 2024

Currently, when discovering a Provider, both openid-configuration and JWKS 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

@ramosbugs
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants