<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Bearer Tokens on Nalar</title>
    <link>https://nalar.dev/tags/bearer-tokens/</link>
    <description>Recent content in Bearer Tokens on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/bearer-tokens/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Limit Bearer Token Damage with Scope and Lifetime</title>
      <link>https://nalar.dev/limit-bearer-token-damage-with-scope-and-lifetime/</link>
      <pubDate>Thu, 03 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/limit-bearer-token-damage-with-scope-and-lifetime/</guid>
      <description>&lt;p&gt;Bearer tokens are convenient because a service can accept a request based on a credential presented with it. That convenience creates a simple security problem: if an attacker obtains a usable bearer token, the attacker may be able to present it too. The receiving service usually cannot distinguish the legitimate holder from a thief merely by possession of the token.&lt;/p&gt;&#xA;&lt;p&gt;The defensive goal is therefore not only to keep tokens confidential. It is also to limit what a stolen token can authorize and how long that authority remains useful. A token that can perform one narrow task for a short period creates a smaller exposure than a long-lived token with broad access.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
