3
Distinguish Between Invalid Credentials and Unverified Accounts During Login
Source: directus/directus#25126 · opened by @TomDrawbridge
Summary Currently, the Directus login API returns a generic INVALID_CREDENTIALS error for both incorrect credentials and unverified accounts (where email verification is enabled but not completed). This makes it impossible to provide accurate feedback to users. I propose adding a distinct ACCOUNT_UNVERIFIED error response. Basic Example Current behavior: Proposed behavior for unverified accounts: Motivation • User Experience: Users currently have no way to know if they entered wrong credentials or just need to verify their email • Reduced Support Requests: Clear messaging reduces "I can't login" support tickets • Compliance: Some industries require clear communication about account status • Conversion Optimization: Allows apps to resend verification emails proactively Detailed Design 1. Modify the authentication service to complete password verification first, then check verification status. The status check m…
No pledges yet. Be the first to back this.
Comments
Similar requests
Allow Unverified Users to Log In and Resend Verification Email
3 votes · 0 comments
Ability to login to directus using access token of a configured provider.
2 votes · 0 comments
Login as arbitrary user when acting as admin
12 votes · 0 comments
Issue INVALID_CREDENTIALS when SSO between Entra ID with Directus 11.5
1 vote · 0 comments
Enable login with JWT from IdP via API
3 votes · 0 comments
No comments yet.