<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Token Validation on Nalar</title>
    <link>https://nalar.dev/tags/token-validation/</link>
    <description>Recent content in Token Validation on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/token-validation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Validate JWTs for the Context That Will Use Them</title>
      <link>https://nalar.dev/validate-jwts-for-the-context-that-will-use-them/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/validate-jwts-for-the-context-that-will-use-them/</guid>
      <description>&lt;p&gt;A service receives a JSON Web Token, verifies its signature successfully, reads the user identifier, and accepts the request. That sounds reasonable, but one question is still unanswered: &lt;strong&gt;was this token issued for this service and this purpose?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;A valid signature proves something narrow. Under the expected cryptographic scheme and key, it shows that the protected token content has not been changed since it was signed by whoever controls that signing key. It does not by itself prove that your API is an intended recipient, that the token is still within its accepted lifetime, or that a token created for one workflow should be accepted by another.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
