Sent to sign in by an app, and back again
An app that uses this forge to sign its people in sends a stranger to /oauth/authorize. The forge sends them on to /signin?next=<that request>; src/web/pages/asking.ts reads the next the way the consent page does, so only a registered client with a registered return address is ever described.
- Who is asking: the sign-in and sign-up pages lead with the return host, the verified part ("gretchy.store wants you to sign in"). The name the app registered follows as small secondary text, escaped, never in the lead: dynamic client registration is open, so a name is whatever its registrant typed. The consent page itself still names only the host.
- Sign up keeps the request: every link between the two forms and from the header carries the page the person came from (
src/web/return_to.ts); a new account ends on the authorize request, so the consent is the next page, not the home page. - A
nextthat is not a registered authorize request says nothing about any app.
Terminal
There is no terminal form of this: the redirect is a browser exchange between the app and the forge. The same account reaches the forge's terminal with an SSH key added under Settings → Keys (ssh <forge>, the exact command is in FORGE_APP_SSH); an account made through an app's sign-up is the same account.
Tests: test/signin-asking.test.ts (including a real-browser walk, skipped where no Chromium runs).