<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Backend For Frontend - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Backend For Frontend Articles feed</description>
    <item>
      <title>Article: The DPoP Storage Paradox: Why Browser-Based Proof-of-Possession Remains an Unsolved Problem</title>
      <link>https://www.infoq.com/articles/dpop-key-storage-unsolved-problem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Backend+For+Frontend-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/dpop-key-storage-unsolved-problem/en/headerimage/dpop-key-storage-unsolved-problem-header-1777296488937.jpg"/&gt;&lt;p&gt;DPoP closes a real gap in OAuth 2.0. Sender-constrained tokens are a meaningful upgrade over bearer tokens for any client that can implement them. But RFC 9449's silence on browser key storage creates the need for an architectural decision that each team must confront deliberately — there is no safe default that works everywhere.&lt;/p&gt; &lt;i&gt;By Dhruv Agnihotri&lt;/i&gt;</description>
      <category>Backend For Frontend</category>
      <category>IndexedDB</category>
      <category>Web Development</category>
      <category>Cloud Security</category>
      <category>Cryptography</category>
      <category>Web Browser</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Thu, 30 Apr 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/dpop-key-storage-unsolved-problem/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Backend+For+Frontend-articles</guid>
      <dc:creator>Dhruv Agnihotri</dc:creator>
      <dc:date>2026-04-30T09:00:00Z</dc:date>
      <dc:identifier>/articles/dpop-key-storage-unsolved-problem/en</dc:identifier>
    </item>
  </channel>
</rss>
