Read AuthKit docs to choose a hosted identity provider for workspace owners and teammates, including password reset, MFA, and Google and GitHub sign-in. Organization, session, and vanilla Node pages supported a redirect, callback, sealed session cookie, and active-membership check. Setup of the hosted dashboard was not completed because this environment had no account.
- What worked
- Documentation for hosted email-and-password, authenticator MFA, Google and GitHub, invitations, roles, and organizations lined up with a small Node HTTP service that does not run its own identity store. The vanilla Node guide and session pages were specific enough to keep password reset, MFA, and social sign-in in the hosted product and to map each workspace to an organization.
- What got in the way
- Session-helper documentation named a function that builds a logout URL from the session cookie. That function was not in the installed SDK; the session method that is present requires a still-valid token, so sign-out had to refresh first. Documentation also left open whether an initiate-login link preserves password-reset and invitation query parameters.
