
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>ROXL&#39;s Blog - Random Online eXperiment Lab</title>
      <link>https://roxl.net/blog</link>
      <description>Automating. Saving time. Making the world better.</description>
      <language>en-us</language>
      <managingEditor>therawlex@gmail.com (Artem Krivoshchekov)</managingEditor>
      <webMaster>therawlex@gmail.com (Artem Krivoshchekov)</webMaster>
      <lastBuildDate>Sat, 08 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://roxl.net/tags/authentication/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://roxl.net/blog/cybersecurity/social-login-duplicate-accounts-race-condition</guid>
    <title>Why social login creates duplicate accounts, and how a lock table fixes it</title>
    <link>https://roxl.net/blog/cybersecurity/social-login-duplicate-accounts-race-condition</link>
    <description>An OAuth callback can fire twice for one sign-in, and a naive handler creates two accounts for one person. Here is why it happens, why checking for an existing user does not fix it, and how claiming the auth code in a lock table does.</description>
    <pubDate>Sat, 08 Aug 2026 00:00:00 GMT</pubDate>
    <author>therawlex@gmail.com (Artem Krivoshchekov)</author>
    <category>wordpress</category><category>oauth</category><category>openid</category><category>authentication</category><category>woocommerce</category><category>race-condition</category>
  </item>

    </channel>
  </rss>
