Both A and B give the person one Google screen and no stray account, even when they sign in from the wrong side of the world. Today's flow needs two Google screens and leaves a stray account. We tested this on one computer with a stand-in for Google and Apple, 5 of 5 runs each.
The spike's pick is B (the broker): it also covers Apple, and it guards every way in. B has five serious gaps that are not fixed yet. They are listed below.
| Way | Google screens | Stray accounts | Apple |
|---|---|---|---|
| Today | 2 when the guess is wrong | 1 in every wrong-guess run | Not measured |
| A: Google first | 1 | 0 | No (needs a code change to Logto) |
| B: broker | 1 | 0 | Yes, 1 Apple screen |
We have two home regions. A person's account lives in one of them. A fresh phone does not know which.
The story in all three drawings: the person lives in Singapore, but is in the United States on a fresh device. Our app guesses by location, so it can guess wrong.
How to read a drawing
Our app must pick a home before it knows who the person is. Here it picks wrong.
What goes wrong today
Our own screen asks Google first. Only then do we pick the home. No guess is needed.
Tested: 1 Google screen and 0 stray accounts, 5 of 5 runs, with the wrong guess. New people and a blocked pop-up also worked (1 run each). Needs no change to Logto and no new service.
The broker is the only thing Google ever talks to. It learns the person once, then answers for Google when the home Logto asks.
Tested: 1 Google screen and 0 stray accounts, 5 of 5 runs, with the wrong guess. Also worked: a new person, Apple (1 Apple screen), a person who starts on the wrong Logto page, and one region's broker stopping mid-sign-in (the other region finished it).
A security review found 5 serious gaps in the test broker. We ran each one against a private copy and all 5 were confirmed. They are the to-do list for the real build, along with 5 more must-fixes of lower risk (10 in all).
1. A stranger's Google login can be finished in your browser. You could end up signed in to the stranger's account.
Fix: tie each login to the browser that started it.
2. The short-lived "just signed in" note can be copied. For its 2 minutes of life it works in other browsers too, and more than once.
Fix: make it single use, and tie it to one browser.
3. That note is stored too widely. Other sites under our login address could read it or plant one. We proved the broker accepts a planted note. We did not run a real browser to prove delivery.
Fix: keep it only for the broker's own address, with the strictest browser rules.
4. If the lookup fails, everyone looks like a new person. They would be signed up in the wrong home.
Fix: on any lookup error show an error page. Only a clear "not found" means new.
5. A leaked broker key lets someone sign in as anyone, in both homes, even people with a password. This follows from how the broker works. It is about key care.
Fix: keep the key in a managed key vault, turn off automatic linking by email for broker sign-ins, and alert on sudden spikes.
The other fixes: single-use codes, check the email is verified, separate Google and Apple settings, limits and timeouts on every outside call, key rotation, and a record of every sign-in the broker issues.
| Question | A: Google first | B: broker |
|---|---|---|
| Google screens (wrong guess) | 1 | 1 |
| Stray accounts | 0 | 0 |
| Apple | No | Yes |
| Person opens a Logto page directly | Not covered | Covered, sent home |
| Secret in the web address | Yes, valid 1 hour | No, lives 1 to 2 minutes |
| New service to run | None | Yes, in every region |
| New master key | None | Yes, one shared key |
| Changes to Logto code | None | None |
| One region down | Not affected | Other region finishes it |
| Fixes needed before production | No full review yet | 10 must-fixes |
A is a strong runner-up if we only ever need Google. B wins when we need Apple or full coverage.
Spike run on 17 Nov 2026. Everything ran locally. Nothing was built for production.