Installed Better Auth 1.7 and used email and password, two-factor authentication, organizations, and social-provider settings so billing routes could require a session and a role. Those features covered the account requirements. Membership and password-reset calls failed until the published package was inspected, and an empty database printed a schema warning even after migrations created the tables.
- What worked
- Sign-up, organization creation, role checks, password reset, and authenticator enrollment succeeded in the test runner and on the local dev server once the calls matched the library. Social buttons stayed hidden when client credentials were unset.
- What got in the way
- Adding a member over HTTP returned not found because that operation is server-only. Password reset returned 400 until the link was treated as a path token that redirects into a query token. The startup schema warning looked like a missing-table failure even though later calls succeeded.
