Repository navigation
docs(google): handle stale app.getgram.ai redirect URIs after the domain move - #227
Open
simplesagar wants to merge 2 commits into
Open
simplesagar wants to merge 2 commits into
simplesagar wants to merge 2 commits into
Conversation
…main move Co-authored-by: Sagar Batchu <simplesagar@users.noreply.github.com>
…in move Speakeasy clients saved after the move to ai.speakeasy.com send the callback on the organization's default host, so a Google web client that lists only the old app.getgram.ai callback rejects them with redirect_uri_mismatch. Each Google guide now tells readers who reuse a client to confirm the callback is listed and add it when missing, and maps redirect_uri_mismatch to that fix. Dossiers and meta.yaml record the Google and Control Plane sources. Co-authored-by: Sagar Batchu <simplesagar@users.noreply.github.com>
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
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.
Why
After the move to
ai.speakeasy.com, Google rejected Scale's connection because their Google OAuth client still listed onlyhttps://app.getgram.ai/mcp/remote_login_callback. Norbert had to swap the URI by hand.The guides never hard-coded the host. They use
{{ gram.oauth.callback_url }}, and speakeasy.com/docs already renders it ashttps://ai.speakeasy.com/mcp/remote_login_callback. The gap is admins with an existing Google client. In Gram, each Speakeasy client keeps the callback origin it was created with, and a Manual client saved from Settings > Identity after the move registers on the organization's default host (server/internal/remotesessions/callbackorigin.go,identitycommit.goatff6a2b2). A Google client that lists only the old callback then returnsredirect_uri_mismatch.What changed
All nine Google guides are updated: Gmail, Calendar, Docs, Drive, People, Sheets, Slides, BigQuery and Compute Engine. BigQuery and Compute Engine are included because they use the same kind of Google web client.
external.md#create-oauth-client: for a reused or shared web client, tells the reader to:{{ gram.oauth.callback_url }}exactly;https://app.getgram.aientry;speakeasy.md: mapsredirect_uri_mismatchat first connection to that fix.research.md/meta.yaml: a "Callback domain change" dossier section and provenance records:doctrine/ai-control-plane-oauth.md.doctrine/ai-control-plane-oauth.mdnow records per-client callback origins, re-pinned to Gramff6a2b2, with adoctrine/CHANGELOG.mdentry.go/generatedis left to the post-merge regen bot.Verification
lint-guide --jsonon all nine guides returns[](no findings).go/internal/gen,go run .) passes.go test ./...passes exceptcmd/supervise-factory, which needs Docker and fails the same way onmain.https://ai.speakeasy.com/mcp/remote_login_callbackleaves no template keys, and both new notes appear.Follow-up outside this repo
The Scale POC Notion page "Google Workspace (Gmail, Calendar, Drive) setup" still hard-codes
https://app.getgram.ai/mcp/remote_login_callbackin step 2.3.Fixes S-1191