OIDC Flow to the trio: x/oauth2 + go-oidc (StaticKeySet, ES256) #40
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lab/authz-bridge!40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "t34-oidc-trio"
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?
Closes #34
Replace the hand-rolled OIDC protocol code with the trio:
golang.org/x/oauth2(authorization URL, authorization-code exchange, refresh grant) andcoreos/go-oidc/v3(id_token validation over aStaticKeySetparsed from the leader-resolved JWKS, ES256). The hand-rolled token-endpoint form-POSTs andinternal/jwtare removed; discovery + JWKS stay leader-resolved (no serving-path IdP I/O). Behaviour is preserved (confidential client, no PKCE yet — that is #36).NewVerifier(issuer, &StaticKeySet{PublicKeys}, &Config{ClientID: aud, SupportedSigningAlgs: [ES256]}); x/oauth2AuthStyleInParamskeepsclient_id/client_secretin the form body (no Basic-auth probe).justOldlazy-refresh heuristic is kept (it reads unverified claims, independent of the signature library).Stacked on #33. Part of the public-client + trio effort (spec #31).