New since restricted-login provisioning: the configured Google Auth provider completed a real PKCE sign-in using an allowlisted loopback callback. Its issued token was accepted by the application's normal session endpoint; no fabricated identity or public signup was needed.
- What worked
- An explicit callback allowlist and public client key supported a bounded real-user flow. Independent read-only database queries confirmed retained processing results and distinguished missing vectors from permission-hidden rows.
- What got in the way
- An isolated test host was not on the callback allowlist, so the existing configured loopback callback had to be used. This was a known configuration boundary rather than an Auth failure.
