Skip to content

Commit 11f16e2

Browse files
committed
Record how the site sign-in door reached staging
Ledger entry for the rollout, and Plan 008 moves to "Uygulanıyor". The order is the part worth keeping. Secrets first, then verify the environment before deploying any code, then the migration, then deploy, then verify again. That middle verification looks redundant and is not: uploading a secret mints a Worker version carrying the previous code, so it is the only thing that proves the already-deployed version survived the change. This is the same shape that took staging down for two nights on 10 August, approached from the other side. The two secrets stay out of REQUIRED_SECRET_BINDINGS and the production config check until production actually has them, since making a binding required fails closed on every version that lacks it. Equinox Rota is registered with openid/profile/email only. Widening later asks the user again, so starting narrow costs nothing and starting wide would hand a site scopes before anyone needed them.
1 parent a2c94a9 commit 11f16e2

2 files changed

Lines changed: 34 additions & 2 deletions

File tree

‎docs/FUTURE_PLANS.md‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -191,11 +191,14 @@ deploy workflow'u ve güvenlik-kritik ortak sözleşmeler.
191191

192192
## Plan 008 — Orbit bütün Equinox siteleri için giriş kapısı
193193

194-
**Durum:** Kabul edildi
194+
**Durum:** Uygulanıyor
195195

196196
**Karar tarihi:** 11 Ağustos 2026
197197

198-
**Uygulama:** Başlamadı. Bu belge tasarım kaydı; kod, uç ve migration yok.
198+
**Uygulama:** Şema, kapsamlar, anahtarlar, ID token imzası, uçlar, onay ekranı
199+
ve panel kartı yazıldı ve 12 Ağustos'ta **staging'e** dağıtıldı. Staging'de
200+
keşif belgesi ve JWKS yayında, Equinox Rota istemci olarak kayıtlı. Production'a
201+
gitmedi; iki sır orada yok ve zorunlu binding listesine bilerek eklenmedi.
199202

200203
**İlk entegrasyon:** Anime sitesi. Oradaki mevcut Google girişi kaldırılıp
201204
yerine yalnız Orbit girişi konacak (karar 11 Ağustos 2026).

‎docs/V6_PROJECT_LEDGER.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2127,3 +2127,32 @@ Anything under `docs/archive/` describes an earlier state and is frozen. Read it
21272127
neither the code nor `wrangler.staging.jsonc` was ever wrong: `npm run
21282128
staging:verify` passes, the forbidden-origin probe is 403 again and an unknown
21292129
`/v1` path is 404 again.
2130+
- The site sign-in door (Plan 008) went to staging on 12 August. Order was
2131+
deliberate and is the order to repeat: upload the two secrets, verify the
2132+
environment BEFORE deploying any code, apply the migration, deploy, verify
2133+
again. The middle step is the one that looks pointless and is not — uploading
2134+
a secret mints a Worker version that inherits the previous code, so the run
2135+
after the upload is the only thing that proves the already-deployed version
2136+
survived it. It did; `staging:verify` passed both times.
2137+
- `ORBIT_OIDC_SIGNING_KEY_V1` and `ORBIT_SITE_TOKEN_PEPPER_V1` are staging
2138+
secrets now, and both are also in the `staging.orbit.sametbasbug` Keychain
2139+
service, which is where the rehearsal scripts read local secrets from. They
2140+
are still NOT in `REQUIRED_SECRET_BINDINGS` or the production config check,
2141+
on purpose: making a binding required takes down every deployed version that
2142+
lacks it, and production has neither secret yet. That step belongs to the
2143+
production rollout, after production has them.
2144+
- Equinox Rota is registered in staging D1 as client `orbit-equinox-rota`, one
2145+
redirect URI, scopes `openid profile email`. Narrow on purpose — the graph and
2146+
posts scopes can be added later, and widening asks the user again rather than
2147+
silently expanding what a site already holds.
2148+
- Three live probes on staging, which together are the reason the redirect
2149+
allowlist exists: a registered client with an allowed redirect and no session
2150+
is parked with a signed `__Host-orbit_site_return` cookie; an unknown client
2151+
answers 400 with no `location` header; a registered client naming an unlisted
2152+
redirect also answers 400 with no `location`. An error sent to an unverified
2153+
address would make the endpoint a courier for whatever address an attacker
2154+
names.
2155+
- The signing key's `kid` is `orbit-oidc-2026-08-11` while the rollout happened
2156+
on the 12th: the generator stamps the UTC date and it was still the 11th in
2157+
UTC. Not worth a rotation, but worth knowing before someone reads the kid as
2158+
a deployment date.

0 commit comments

Comments
 (0)