<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>jwt vs token on Kuldeep Pisda</title><link>https://kdpisda.in/tag/jwt-vs-token/</link><description>Recent content in jwt vs token on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Oct 2025 15:28:57 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/jwt-vs-token/index.xml" rel="self" type="application/rss+xml"/><item><title>A Guide to Django REST Framework Authentication That Won't Put You to Sleep</title><link>https://kdpisda.in/a-guide-to-django-rest-framework-authentication-that-wont-put-you-to-sleep/</link><pubDate>Wed, 29 Oct 2025 15:28:57 +0530</pubDate><guid>https://kdpisda.in/a-guide-to-django-rest-framework-authentication-that-wont-put-you-to-sleep/</guid><description>&lt;p&gt;Let&amp;rsquo;s be honest. Setting up &lt;strong&gt;Django REST Framework authentication&lt;/strong&gt; can feel like assembling IKEA furniture in the dark. You know all the pieces are there—sessions, tokens, JWTs—but the instructions seem written in another language, and you have this nagging fear that one wrong move will leave your API wide open.&lt;/p&gt;
&lt;p&gt;I have been there. I once got stuck on a bug for hours before realizing my frontend was sending the &lt;code&gt;Authorization&lt;/code&gt; header with a lowercase &amp;ldquo;a&amp;rdquo;. It&amp;rsquo;s the kind of thing that makes you question your life choices.&lt;/p&gt;</description></item></channel></rss>