are there other options that could be explored to tune down the number of requests per day?
some ideas:
hardcode a high refresh cycle time
allow the user to configure the cycle time with an environmental variable
refresh the key only when needed, rather than on a cycle
i haven't yet dug into this, so i don't know if (3) is viable. (2) would help users who don't need this level of freshness tune the requests down while a default value would leave the service unchanged for others.
this issue branched from a related discussion in: #660
Originally created by @eleith on GitHub (Aug 1, 2025).
starting at https://github.com/moghtech/komodo/commit/3f767ed42e328be6887ee0b8b330669d6810dc44, Komodo refreshes it's oidc JWK every 60 seconds, leading to at minimum 1440 request per day (double in many cases due to first fetching of `.well-known` before fetching the `jwk` endpoint).
are there other options that could be explored to tune down the number of requests per day?
some ideas:
1. hardcode a high refresh cycle time
2. allow the user to configure the cycle time with an environmental variable
3. refresh the key only when needed, rather than on a cycle
i haven't yet dug into this, so i don't know if (3) is viable. (2) would help users who don't need this level of freshness tune the requests down while a default value would leave the service unchanged for others.
this issue branched from a related discussion in: #660
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @eleith on GitHub (Aug 1, 2025).
starting at https://github.com/moghtech/komodo/commit/3f767ed42e328be6887ee0b8b330669d6810dc44, Komodo refreshes it's oidc JWK every 60 seconds, leading to at minimum 1440 request per day (double in many cases due to first fetching of
.well-knownbefore fetching thejwkendpoint).are there other options that could be explored to tune down the number of requests per day?
some ideas:
i haven't yet dug into this, so i don't know if (3) is viable. (2) would help users who don't need this level of freshness tune the requests down while a default value would leave the service unchanged for others.
this issue branched from a related discussion in: #660