<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JWT on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/jwt/</link><description>Recent content in JWT on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 11 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/jwt/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 5: User Management: Authentication &amp;amp; Authorization (JWT)</title><link>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/05-auth-jwt/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/scalable-nodejs-api-platform/05-auth-jwt/</guid><description>&lt;h2 id="chapter-5-user-management-authentication--authorization-jwt"&gt;Chapter 5: User Management: Authentication &amp;amp; Authorization (JWT)&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 5! In this crucial phase of our journey, we&amp;rsquo;ll dive deep into securing our application by implementing robust user authentication and authorization. This involves enabling users to register for an account, log in, and then access protected resources based on their authenticated status. We&amp;rsquo;ll leverage JSON Web Tokens (JWT) as our primary mechanism for stateless authentication, a cornerstone of modern API security.&lt;/p&gt;</description></item><item><title>Chapter 8: Authentication &amp;amp; Authorization: Token Management and Guards</title><link>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/auth-token-management-guards/</link><pubDate>Wed, 11 Feb 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/angular-production-guide-2026/auth-token-management-guards/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 8! In the exciting world of web applications, knowing &lt;em&gt;who&lt;/em&gt; a user is (authentication) and &lt;em&gt;what&lt;/em&gt; they&amp;rsquo;re allowed to do (authorization) is paramount. Without these, your application is an open book, vulnerable to unauthorized access and data breaches. This chapter dives deep into implementing robust authentication and authorization mechanisms in your modern Angular v20.x standalone application.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll move beyond simple login forms to understand the lifecycle of JSON Web Tokens (JWTs), how to securely manage them, and how to gracefully handle token expiration with silent refresh flows. You&amp;rsquo;ll learn how to safeguard your application&amp;rsquo;s routes using functional Angular Route Guards and implement granular, role-based access control. By the end of this chapter, you&amp;rsquo;ll have a solid understanding of how to build a secure, enterprise-grade authentication system that provides a seamless user experience.&lt;/p&gt;</description></item><item><title>Chapter 8: Session Management &amp;amp; Token-Based Attacks</title><link>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/session-token-attacks/</link><pubDate>Sun, 04 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/web-security-ethical-hacking-2026/session-token-attacks/</guid><description>&lt;h2 id="introduction-to-session-management--token-based-attacks"&gt;Introduction to Session Management &amp;amp; Token-Based Attacks&lt;/h2&gt;
&lt;p&gt;Welcome back, future security expert! In the previous chapters, we laid the groundwork for understanding web application vulnerabilities and basic authentication. Now, it&amp;rsquo;s time to elevate our game and tackle one of the most critical aspects of web security: how applications maintain state and identify users across multiple requests. This is where &lt;strong&gt;session management&lt;/strong&gt; and &lt;strong&gt;token-based authentication&lt;/strong&gt; come into play.&lt;/p&gt;
&lt;p&gt;Think of a session as your temporary identity card for a website after you log in. The way this &amp;ldquo;card&amp;rdquo; is issued, stored, and verified is paramount to security. A flaw here can lead to an attacker impersonating you, accessing your data, or even taking over your account entirely. We&amp;rsquo;ll explore various session mechanisms, from traditional session IDs to modern JSON Web Tokens (JWTs), dissecting their vulnerabilities, and, most importantly, learning how to defend against sophisticated attacks.&lt;/p&gt;</description></item><item><title>Chapter 15: Securing Your API with Spring Security 6</title><link>https://ai-blog.noorshomelab.dev/java-mini-projects/ch15-spring-security-api/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/java-mini-projects/ch15-spring-security-api/</guid><description>&lt;h2 id="chapter-15-securing-your-api-with-spring-security-6"&gt;Chapter 15: Securing Your API with Spring Security 6&lt;/h2&gt;
&lt;p&gt;Welcome to Chapter 15! In this crucial chapter, we&amp;rsquo;re going to elevate the &amp;ldquo;Basic To-Do List Application&amp;rdquo; you&amp;rsquo;ve been building by implementing robust security measures. A production-ready application, especially one exposing an API, absolutely requires authentication and authorization to protect its resources from unauthorized access and malicious activity.&lt;/p&gt;
&lt;p&gt;We will integrate Spring Security 6, the latest iteration of the powerful security framework for Spring applications, to secure our To-Do API. This involves setting up user authentication using JSON Web Tokens (JWT) for stateless API communication and defining authorization rules to control access to specific endpoints based on user roles. By the end of this chapter, you will have a fully secured To-Do List API, where users must log in to obtain a token, and then use that token to interact with their To-Do items.&lt;/p&gt;</description></item><item><title>How JWT Authentication Works: Deep Dive into Internals</title><link>https://ai-blog.noorshomelab.dev/how-it-works/how-jwt-authentication-works/</link><pubDate>Wed, 21 Jan 2026 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/how-it-works/how-jwt-authentication-works/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. It has become a cornerstone of modern web authentication and authorization, particularly in the realm of stateless APIs, microservices, and mobile applications. JWTs enable secure and efficient communication by allowing servers to verify the authenticity and integrity of client requests without needing to store any session-specific information on their end.&lt;/p&gt;</description></item><item><title>Chapter 4: Basic User Authentication with JWT</title><link>https://ai-blog.noorshomelab.dev/chat-guide/chapter-4-basic-auth/</link><pubDate>Wed, 20 Aug 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/chat-guide/chapter-4-basic-auth/</guid><description>&lt;p&gt;Before users can chat, we need to know who they are. This chapter focuses on implementing a basic user authentication system using JSON Web Tokens (JWT) in FastAPI. JWTs are a common, secure way to transmit information between parties as a JSON object, ideal for stateless authentication in APIs.&lt;/p&gt;
&lt;h3 id="purpose-of-this-chapter"&gt;Purpose of this Chapter&lt;/h3&gt;
&lt;p&gt;By the end of this chapter, you will:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Understand what JWTs are and why they are used for authentication.&lt;/li&gt;
&lt;li&gt;Set up libraries for password hashing and JWT generation.&lt;/li&gt;
&lt;li&gt;Implement user creation and login endpoints.&lt;/li&gt;
&lt;li&gt;Create a dependency to protect FastAPI routes with JWT.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="concepts-explained-jwt-and-hashing"&gt;Concepts Explained: JWT and Hashing&lt;/h3&gt;
&lt;h4 id="json-web-tokens-jwt"&gt;JSON Web Tokens (JWT)&lt;/h4&gt;
&lt;p&gt;A JWT is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object and are digitally signed using a secret (with HMAC algorithm) or a public/private key pair (with RSA or ECDSA).&lt;/p&gt;</description></item></channel></rss>