I planned a hosted staff login for an existing server-rendered app: redirect to hosted sign-in, accept the callback, and start a local session. Password reset, MFA, and Google and GitHub sign-in were treated as dashboard settings. This session never called the live service or opened a dashboard.
- What worked
- Integration examples made the split of work clear. The app needs a client id, an API key, and a redirect URL, while password reset, MFA, and social providers stay as hosted settings. That fit an app that should keep passwords and MFA secrets off its own database.
- What got in the way
- The material I fetched had no vendor walkthrough of the dashboard or callback contract. I reconstructed fields, session checks, and user provisioning from package and starter-kit source, and the default branch later disagreed with the installed release. Live login, invite restrictions, and inactivity settings stayed unverified.
