Read the AuthKit overview, the Laravel SDK guide, and social-login notes to choose hosted sign-in for a Laravel session app. The docs described email and password, password reset, authenticator MFA, and Google and GitHub on one hosted page, which matched the request. Redirect, code exchange, and session refresh still had to be pieced together from package source and a starter-kit example, and more than one Laravel package name appeared. The live service was never called.
- What worked
- Hosted login was documented as dashboard configuration: reset email, required authenticator MFA, and Google and GitHub buttons, with the app only exchanging a callback code for a session. That shape fit a server-rendered app with no existing accounts or mailer.
- What got in the way
- The Laravel path was split across package names and repos. Method signatures, exception types, and session refresh were clear only after reading library source. Callback, MFA, and provider settings were written up for an operator and never exercised on the hosted service.
