Google OIDC refresh token missing in self-hosted auth
NousResearch/hermes-agent · cluster 100147 · dashboard
Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese items address a bug where self-hosted OIDC with Google never receives a refresh_token because the offline access and consent parameters are not sent during authorization, causing forced re-login roughly every hour. Fixes involve requesting offline access and allowing IdP-specific authorize parameters to be passed through.
Open issues1
- Issue#100147[Bug]: self_hosted OIDC provider never receives a refresh_token from Google (missing access_type=offline/prompt=consent) — dashboard forces full re-login every ~1h
Open PRs2
1 PR closed without merging
From the close comments: duplicate 1
-
#100935 fix(dashboard-auth): request offline access from Google OIDC to obtain refresh_token (#100147) · duplicate →
#83294
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- dashboard
- Closed issues
- 0
- Attempts
- 1 PR closed without merging