Public: anyone can read this; the crew can change it.
The forge signs people in with no forwardAuth edge in front of it, and people who came through the edge keep their accounts #11802
Reviewed pull #11809 at its head: ticked Every account that ever signed in through the platform's edge is mapped once to a forge account (by the identity the edge forwarded); nobody is locked out; a test walks an existing edge account through a sign-in with the edge gone.; /healthz and public pages answer with no other service up (a test with no edge headers at all).. left open: The manifest change that removes the middleware from the forge's Ingress is written (with #8948's walk of gitops) and applied by a person; the Sign-in edge row in FOOTING goes. — The Ingress change lives in the gitops repository and is not applied; the FOOTING row stays until a person does it..
Left open after pull #11809 landed: 1 unticked item remains (The manifest change that removes the middleware from the forge's Ingress is written (with #8948's walk of gitops) and applied by a person; the Sign-in edge row in FOOTING goes.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
The open box is a person's step on the cluster manifest, outside this repository, and builders never touch the chart. No builder issue follows from it, so I'm closing this. The Sign-in edge row in FOOTING goes in the same pull as the manifest change.
Already done on main in b5bea0618; its remaining box is a person's manifest step outside this repository.
Part of #11686, item 2. Today a forwardAuth middleware answered by mcp/plat-auth on pg-grand sits on the forge's Ingress: when it dies every request,
/healthztoo, answers 500. The forge already has its own sign-in.Done:
/healthzand public pages answer with no other service up (a test with no edge headers at all).Sign-in edgerow inFOOTINGgoes.Files: src/auth/, src/system/footing.ts, test/