Repository navigation
Use case with customer-configured providers #341
Description
Hello guys,
We build a product where customers can configure their OIDC connections themselves and I wanted to ask you if you cover such a use case. The challenge is that we can have tens of thousands of OIDC configs (and growing), and we can't really start a GenServer for each one of them, while the API of oidcc looks like it takes provider_configuration_name which is basically a process name.
Right now we are using https://github.com/firezone/openid_connect (that we fully rewrote to have a limited cache size) and would like to give oidcc a try.
Do you have any ideas if we will be able to use it in a similar manner? Maybe some refs to the docs would help. If not, would you want a PR to make it possible?
Activity
maennchen commentedon Apr 12, 2024
You should be able to manage the configurations yourself as well. To do so, you can create a context and then use it:
The functions in
oidccare only convenience functions and you should be able to call underlying functions with a manually created context.If you opt in to use this method, you’ll be responsible to manage loading and refreshing the configuration.
Make sure yo implement a
refresh_jwksfunction as well to reload the jwks any time you encounter a new and unknownkid.