{"repo":"NousResearch/hermes-agent","public_id":"100147","display_label":"Google OIDC refresh token missing in self-hosted auth","summary":"These 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.","subsystem":"dashboard","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":100147,"title":"[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","url":null,"state":"open"},{"kind":"pr","number":83294,"title":"fix(dashboard-auth): request offline access for Google OIDC","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"d20d37e5e0","number":0},{"kind":"pr","value":"#100147","number":100147},{"kind":"pr","value":"#53835","number":53835}],"category":"merged_via","implication":"superseded"},"merged":false},{"kind":"pr","number":100157,"title":"fix(dashboard-auth): let self-hosted OIDC pass IdP-specific authorize params","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":100935,"title":"fix(dashboard-auth): request offline access from Google OIDC to obtain refresh_token (#100147)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#83294","number":83294}],"category":"duplicate_of","implication":"duplicate"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}