Should self-hosted auth servers separate username from email
A developer building a self-hosted OIDC/OAuth identity server is unsure whether to support separate username and email fields, weighing added complexity (uniqueness rules, recovery flows, migrations) against unclear real-world benefit, and is soliciting concrete cases from other builders.
Signal
Visibility
Sign in free to unlock the full scoring breakdown, root-cause analysis, and solution blueprint.
Sign up freeAlready have an account? Sign in
Deep Analysis
Root causes, cross-domain patterns, and opportunity mapping
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Solution Blueprint
Tech stack, MVP scope, go-to-market strategy, and competitive landscape
Sign up free to read the full analysis — no credit card required.
Already have an account? Sign in
Similar Problems
surfaced semanticallyStructuring a Personal Email Domain Setup for Privacy and Longevity
A user seeks advice on the ideal long-term personal email domain setup, weighing custom domains, per-signup unique aliases, and a separate family domain for privacy. Replies show the space is already served by several named tools and services, indicating an advice-seeking discussion rather than an unmet need.
Trello Account Recovery and Login Confusion Blocks Client Notifications
External clients invited to Trello frequently forget which method they used to sign up, locking them out of project notifications. Account management lacks adequate recovery flows for occasional users. This creates support overhead for the teams managing the boards.
Gusto Login Process Causes Confusion With Multiple Email Accounts
Users find Gusto's login frustrating when they have registered with a different email than their primary one. User-side account management issue rather than a product deficiency. Minimal signal for product improvement.
Authentication UX Causes Abandonment Among Senior Users
Users aged 65+ consistently struggle with password-based authentication flows, confusing multi-account OAuth redirects, and forgot-password recovery processes. SaaS operators serving this demographic report high abandonment rates despite simplification efforts. No senior-focused auth UX library exists.
Gusto Requires Separate Logins for Users with Multiple Employers
Workers with two jobs on Gusto must maintain separate accounts and sign-ins for each employer, creating friction when checking pay or hours across jobs. There is no unified login to manage multiple employer relationships within one account.
Problem descriptions, scores, analysis, and solution blueprints may be updated as new community data becomes available.