<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Auth on Commentary of Takao</title><link>https://takao.blog/en/tags/auth/</link><description>Recent content in Auth on Commentary of Takao</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Commentary of Takao</copyright><lastBuildDate>Sat, 13 Jun 2026 23:11:50 +0900</lastBuildDate><atom:link href="https://takao.blog/en/tags/auth/index.xml" rel="self" type="application/rss+xml"/><item><title>Comparing JWT Tokens vs Stateful Sessions in Web Security</title><link>https://takao.blog/en/web/security-jwt-vs-session-auth/</link><pubDate>Fri, 20 Mar 2026 00:00:00 +0900</pubDate><guid>https://takao.blog/en/web/security-jwt-vs-session-auth/</guid><description>&lt;img src="https://takao.blog/img/thumnail.webp" alt="Featured image of post Comparing JWT Tokens vs Stateful Sessions in Web Security" /&gt;&lt;h2 id="introduction"&gt;Introduction
&lt;/h2&gt;&lt;p&gt;Authentication is the backbone of every web application. Two dominant patterns have emerged: &lt;strong&gt;stateless JWT (JSON Web Token)&lt;/strong&gt; auth and &lt;strong&gt;stateful session-based&lt;/strong&gt; auth. Both solve the same problem — verifying who a user is on subsequent requests — but they differ fundamentally in storage, revocation, and security properties. This article provides a detailed comparison to help you choose the right approach for your application.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="jwt-structure"&gt;JWT Structure
&lt;/h2&gt;&lt;p&gt;A JWT is a self-contained token consisting of three base64url-encoded segments separated by dots:&lt;/p&gt;</description></item></channel></rss>