Social or OAuth signup is available
Why it matters
Email-and-password-only signup forces users to generate another credential pair and commit to a password before trusting the product. OAuth signup cuts that friction to one click and typically lifts conversion 20-40% on consumer SaaS, while also improving the access-control posture by offloading password storage, credential rotation, and MFA to an identity provider the user already trusts. Skipping OAuth leaves conversion gains on the table and pushes you into the password-handling responsibilities the user-experience and access-control taxons warn against.
Severity rationale
Low because the product still functions without OAuth; the cost is conversion drag, not a broken flow.
Remediation
Wire at least one OAuth provider into your auth configuration and surface a button for it above the email/password form. Edit src/lib/auth.ts (or auth.config.ts depending on your auth library) and add a provider block, then render a "Continue with Google" button on the signup page.
providers: [
GoogleProvider({ clientId: process.env.GOOGLE_ID!, clientSecret: process.env.GOOGLE_SECRET! }),
GithubProvider({ clientId: process.env.GITHUB_ID!, clientSecret: process.env.GITHUB_SECRET! }),
]
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Onboarding UX Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from saas-onboarding·automated