Publish verifiable Google OIDC signing keys - #32
Merged
Merged
Conversation
RhysSullivan
marked this pull request as ready for review
September 23, 2026 17:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Google ID tokens were signed with HS256 while discovery published an empty key set. OIDC clients such as Better Auth rejected sign-in. Sign tokens with RS256 and a key ID, and publish the matching public JWK. Keys are generated lazily and last for the server process, like the existing Apple emulator.
Verified: all 21 Google tests pass, including real authorization-code exchange, discovery-key verification, and rejection of tampered tokens and wrong audiences. The new regression fails against the original implementation. Google typecheck and lint pass (two existing unused-variable warnings). Documentation and CLI help describe the behavior.
Required by the Executor test-suite repair. No hosted deployment is included in this PR.