<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Prath</title>
    <description>The latest articles on DEV Community by Prath (@prath47).</description>
    <link>https://dev.to/prath47</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3881697%2F5f8f0e0d-49c5-4067-b758-15f183429564.jpeg</url>
      <title>DEV Community: Prath</title>
      <link>https://dev.to/prath47</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/prath47"/>
    <language>en</language>
    <item>
      <title>Hmm....🚨 OAuth vs Email Signup Conflict — Security or Bad UX? (Need your opinion)</title>
      <dc:creator>Prath</dc:creator>
      <pubDate>Thu, 16 Apr 2026 15:14:27 +0000</pubDate>
      <link>https://dev.to/prath47/hmm-oauth-vs-email-signup-conflict-security-or-bad-ux-need-your-opinion-1df6</link>
      <guid>https://dev.to/prath47/hmm-oauth-vs-email-signup-conflict-security-or-bad-ux-need-your-opinion-1df6</guid>
      <description>&lt;p&gt;Hello guys, &lt;br&gt;
This is my first post. Apologies if any mistake is there.&lt;/p&gt;

&lt;p&gt;So in the morning i came across this git issue on the appwrite git repo #11908.&lt;/p&gt;

&lt;p&gt;🧪 Scenario&lt;br&gt;
A user signs up using Google OAuth (&lt;a href="mailto:myemail@google.com"&gt;myemail@google.com&lt;/a&gt;)&lt;br&gt;
Then tries to sign up again using email/password (account.create())&lt;/p&gt;

&lt;p&gt;🤔 Expected Behavior&lt;br&gt;
Appwrite should return:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"A user with the same id, email, or phone already exists in this project."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"code"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;409&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"user_already_exists"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;😕 Actual Behavior&lt;br&gt;
Instead, it returns:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"message"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"There was an error processing your request."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"code"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="mi"&gt;400&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;&lt;span class="w"&gt;
  &lt;/span&gt;&lt;span class="nl"&gt;"type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="w"&gt; &lt;/span&gt;&lt;span class="s2"&gt;"general_bad_request"&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="w"&gt;
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;🧠 What's Going On?&lt;/p&gt;

&lt;p&gt;In the codebase, this seems intentional:&lt;br&gt;
“Return a generic bad request to prevent exposing existing accounts”&lt;br&gt;
So this is clearly a security decision to avoid account enumeration.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7enigpyxpfufixqn9wzg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F7enigpyxpfufixqn9wzg.png" alt=" "&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;BUT…&lt;/p&gt;

&lt;p&gt;⚖️ The Inconsistency&lt;/p&gt;

&lt;p&gt;If a user signs up normally (email/password) and tries again →&lt;br&gt;
Appwrite does return 409 user_already_exists&lt;/p&gt;

&lt;p&gt;So:&lt;/p&gt;

&lt;p&gt;Case    Response&lt;br&gt;
Email → Email again 409 (explicit)&lt;br&gt;
OAuth → Email 400 (generic)&lt;/p&gt;

&lt;p&gt;This means:&lt;br&gt;
👉 Enumeration is already possible&lt;br&gt;
👉 But UX is bad only in OAuth cases&lt;/p&gt;

&lt;p&gt;💥 Why This Matters&lt;/p&gt;

&lt;p&gt;For real apps:&lt;/p&gt;

&lt;p&gt;Users get confused (“Did I already sign up?”)&lt;br&gt;
No clear path to login instead&lt;br&gt;
Poor first impression of auth flow&lt;/p&gt;

&lt;p&gt;❓ The Real Question&lt;/p&gt;

&lt;p&gt;What should be the correct behavior here?&lt;/p&gt;

&lt;p&gt;Option A — Security First 🔒&lt;br&gt;
Always return generic errors (400)&lt;br&gt;
➡️ Prevents enumeration, but hurts UX&lt;/p&gt;

&lt;p&gt;Option B — Consistency + UX 👍&lt;br&gt;
Always return 409 user_already_exists&lt;br&gt;
➡️ Better UX, but leaks account existence&lt;/p&gt;

&lt;p&gt;Option C — Smarter Approach 🧠&lt;br&gt;
Return 409&lt;br&gt;
BUT guide user: “Try logging in with Google”&lt;br&gt;
Or auto-link identities&lt;br&gt;
💬 I’d Love Your Thoughts&lt;br&gt;
How do you handle this in your apps?&lt;br&gt;
Is account enumeration still a real concern here?&lt;br&gt;
Should OAuth + email accounts be auto-linked?&lt;/p&gt;

&lt;p&gt;Let’s discuss 👇&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>github</category>
      <category>appwritehack</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
