Chose hosted login for email and password, password reset, authenticator MFA, and Google and GitHub sign-in, and wired the API to start that flow and accept its access tokens. Vanilla client docs and the session-token reference were enough to shape redirects and bearer checks. Login-start query parameters, screen hints, and password-reset or invitation returns took several extra searches. A local login request produced a redirect toward the hosted login host. Reset, MFA, and social sign-in were not completed against a live tenant.
- What worked
- The hosted product covered every required customer flow without a custom login UI, including built-in Google and GitHub providers and a path to later enterprise sign-in. Session-token material was specific enough to validate access tokens against the provider signing keys and keep application accounts in the existing database.
- What got in the way
- Documentation did not answer, in one place, how to start login, pass a screen hint, or return from password reset and invitations. Those details needed repeated searches and a look at the client library. Hosted reset, MFA, and social flows were never executed on a real tenant, so their runtime behavior is unrated.
