Skip to content

Publish the Google OAuth consent screen: domain verification, policy links, review #86

Open

Description

@Lin1er

Owner: James (@Lin1er) · Branch: none (Google Cloud console setup) · Milestone: M3 · Blocked by: #85 (privacy and terms pages) · Needs from @AncungAulia: one DNS TXT record on forepay.xyz

Why

The OAuth consent screen behind the AdSense sign-in (#78) is in Testing. Only Google accounts added by hand as test users can sign in. Everyone else, a judge included, gets "Access blocked". Publishing the screen removes that limit for the demo and beyond.

Steps

1. Prove we own forepay.xyz

  • In Google Search Console, add a Domain property for forepay.xyz. Use the Google account that owns the Cloud project, so the two are linked.
  • Google gives a TXT record. @AncungAulia adds it at the DNS provider for forepay.xyz, then it gets verified.

2. Branding (Google Auth Platform → Branding)

3. Data access

  • The only scope is https://www.googleapis.com/auth/adsense.readonly.

  • If the console marks it sensitive, write the justification: "Reads one AdSense report, the estimated earnings total in USD for the last three complete months, so the creator can prove that figure in a zero-knowledge proof and request a revenue-based advance. Read-only; nothing is stored."

  • If a demo video is required, record it. It should show:

    • the consent screen with the scope;
    • the sign-in from the front end;
    • what is done with the data (the proof and the offer).

    Upload it to YouTube as unlisted. The deployed front end (Deploy the front end and capture the screenshots #22) makes this easier.

4. Origins

  • Add the deployed front end's origin to the OAuth client's Authorized JavaScript origins.
  • Add the same origin to the relay's CORS_ORIGINS.

5. Publish

  • Audience → Publish app. If verification is required for the scope, submit it.

What to expect while Google reviews it: sensitive scopes are reviewed by Google, and that can take days or longer. Until the review passes, a published app can still be used, but Google shows an "unverified app" warning and caps the number of users. For a demo that is acceptable, but the timing is why this starts now.

Done when

  • A Google account that is not on the test user list can sign in through the popup on the deployed front end. The "unverified app" warning is acceptable while review is pending.
  • The verification status (submitted, or approved) is recorded in a comment here.

Working agreement

  1. One issue, one owner. 2. Branch per issue, named above — not the GitHub-suggested one. 3. MCP Stellar Raven for any Stellar/Soroban fact that gets written down. 4. Merge through PR review by Axel (PM); no self-merge. If an ACC has not arrived within two days on something already verified, merge and say so in the PR. 5. Deploys need evidence: contract address or tx hash on stellar.expert, recorded in docs/deployments.md. 6. Secrets live in .env, gitignored, chmod 600 — never printed, never committed, never pasted into an issue or PR. Only public G… and C… addresses appear anywhere. 7. Issues, commits and PRs in English.

Activity

  1. self-assigned this
    on Oct 21, 2026
  2. added
    M3-appWeek 3 — proof relay and the creator front end
    on Oct 21, 2026
  3. Lin1er commented on Oct 23, 2026

    @Lin1er
    CollaboratorAuthor

    Step 4, relay half: done. https://app.forepay.xyz is in the relay's CORS_ORIGINS and checked live; recorded in #87. Still to do here: add the same origin to the OAuth client's Authorized JavaScript origins in the Google Cloud console.

  4. Lin1er commented on Oct 23, 2026

    @Lin1er
    CollaboratorAuthor

    Step 4 done: https://app.forepay.xyz is now in the OAuth client's Authorized JavaScript origins too (2026-10-23), next to http://localhost:3000.

  5. added a commit that references this issue on Oct 23, 2026
  6. Lin1er commented on Oct 25, 2026

    @Lin1er
    CollaboratorAuthor

    #85 is done (#88, merged 2026-10-23), and both pages are live as of 2026-10-25:

    Next on this issue: verify forepay.xyz in Search Console (a TXT record on the domain, @AncungAulia), then put these two links in Branding and submit for review.

  7. Lin1er commented on Oct 27, 2026

    @Lin1er
    CollaboratorAuthor

    Step 5 done: the consent screen is published (In production) as of 2026-10-27. It is no longer in Testing, so a Google account does not need to be on the test-user list to sign in.

    Still open for "Done when":

    • A Google account that is not a test user signs in through the popup on https://app.forepay.xyz. The "unverified app" warning is acceptable.
    • The verification status (submitted or approved) is recorded here.

    Next on top of this, #98: admob.readonly goes on the same consent screen. The legal-page half is drafted on #105, and the policy has to name the scope before it is submitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

M3-appWeek 3 — proof relay and the creator front end

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions