Publish verifiable Google OIDC signing keys - #28
Draft
RhysSullivan wants to merge 1 commit into
Draft
RhysSullivan wants to merge 1 commit into
RhysSullivan wants to merge 1 commit into
Conversation
RhysSullivan
added this pull request to stack #30
September 20, 2026 03:17
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 OIDC advertised an empty JWKS and signed tokens with a shared HMAC secret. OAuth clients that require signature verification could not use it.
Sign ID tokens with per-instance RS256 keys, publish only public keys with a matching key ID, and persist signing material in the existing instance snapshot. Discovery and service coverage now describe that behavior.
Validation: Google type check and package builds passed. A real HTTP OAuth exchange against the running Worker passed signature, issuer, audience, nonce and verified-email checks. The deployed emulators.dev instance publishes an RSA/RS256 public key. Google lint reports two existing warnings and no errors.