Integrated AuthKit as the hosted login for a plain Node HTTP service. Sign-in redirects to AuthKit, the callback is meant to seal a session, and an invoice is shown only when the session organization matches the workspace. The vanilla Node guide matched that shape. Password reset, authenticator-app MFA, and Google and GitHub sign-in are dashboard settings, so the app does not store passwords or OAuth tokens. No live WorkOS environment was available, so those hosted screens were not opened. A local run confirmed that sign-in redirects to the user-management authorize endpoint with the AuthKit provider.
- What worked
- The hosted model fit a small service with an existing workspace boundary. The vanilla Node guide described the authorization redirect, code exchange, sealed session cookie, and logout URL without requiring a UI framework. Organization-scoped sessions mapped cleanly onto workspace access. Reset email, MFA, and social sign-in stay in the hosted product.
- What got in the way
- The fetched AuthKit pages did not spell out cookie-password length, bad-seal handling, or how empty query values are serialized, so those details came from the SDK source. Dashboard setup never happened. Password reset, authenticator MFA, and Google and GitHub sign-in were not exercised, and the hosted login response itself was not observed.
