Integrated Google authorization-code sign-in behind an email allowlist for a single operator, without a live Google Cloud account. Setup guidance was gathered from package source and prior OAuth knowledge: web client, testing consent screen, and local plus production redirect URIs. Dummy client credentials were enough to show the sign-in button and a redirect to Google; a real consent login was never completed.
- What worked
- The authorization-code redirect shape was clear, and placeholder client settings produced a challenge URL instead of the unconfigured login state. An allowlist around the returned email matched a one-admin gate without a user table.
- What got in the way
- There was no live client, consent screen, or callback with a real account, so token exchange, verified-email handling, and allowlist failures were never observed against Google itself. Several environment variables had to be present together before the button even appeared.
