I read AuthKit's hosted-login, session, logout, pricing, and Google and GitHub OAuth docs to add managed sign-in to a small Node service with no identity store. Those pages described password reset, authenticator-app MFA, and social sign-in well enough to implement a redirect and sealed-session adapter. No tenant was available, so I never opened a live AuthKit login.
- What worked
- The guides named the hosted flows this service needed, including forgot-password email that revokes sessions, required authenticator MFA set in the dashboard, and Google and GitHub on the same login page. Pricing material indicated those user-management features stay free at a volume far above a very small team. Staging versus production ownership of GitHub credentials was also explicit.
- What got in the way
- The vanilla Node example still obtains a logout URL in a way that rechecks the session token. The client source showed that call fails after the token expires, so the documented path was not safe to copy. I also could not confirm dashboard MFA or OAuth setup against a real tenant.
