github-starred/komodo
2
0
Fork 1
mirror of https://github.com/moghtech/komodo.git synced 2026-05-07 02:16:06 -05:00
Code Issues 3.5k Packages Projects Releases 103 Wiki Activity

[GH-ISSUE #702] allow users to reduce or configure oidc jwk checks #6268

New Issue
Open
opened 2026-04-24 19:25:13 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-24 19:25:13 -05:00
Owner
Copy Link

Originally created by @eleith on GitHub (Aug 1, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/702

starting at 3f767ed42e, 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

Originally created by @eleith on GitHub (Aug 1, 2025). Original GitHub issue: https://github.com/moghtech/komodo/issues/702 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
GiteaMirror added the enhancement label 2026-04-24 19:25:13 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.19.0
1.19.1
1.19.2
1.19.3
1.19.4
2.0.0
bug
documentation
done
enhancement
help wanted
info
pull-request
Mirrored from GitHub Pull Request
 question
security
seen 👀
setup
thinking 🤔
ui
v2
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/komodo#6268
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?