<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Access Tokens on Nalar</title>
    <link>https://nalar.dev/tags/access-tokens/</link>
    <description>Recent content in Access Tokens on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/access-tokens/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>DPoP Binds OAuth Access Tokens to a Client Key</title>
      <link>https://nalar.dev/dpop-binds-oauth-access-tokens-to-a-client-key/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/dpop-binds-oauth-access-tokens-to-a-client-key/</guid>
      <description>&lt;h1 id=&#34;dpop-binds-oauth-access-tokens-to-a-client-key&#34;&gt;DPoP Binds OAuth Access Tokens to a Client Key&lt;/h1&gt;&#xA;&lt;p&gt;A bearer access token is usable by any party that obtains the token and can present it to the resource server. TLS protects the token while it crosses a correctly authenticated connection, but it does not change that bearer property after the token reaches an endpoint, log, process, browser context, or other storage location.&lt;/p&gt;&#xA;&lt;p&gt;Demonstrating Proof of Possession (DPoP), specified by RFC 9449, adds a key-bound layer at the application protocol. The client creates an asymmetric key pair and signs a DPoP proof JWT. An authorization server can bind an issued access token to the public key represented by that proof. The resource server then requires both the token and a valid proof created with the corresponding private key.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
