<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spring Security on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/spring-security/</link><description>Recent content in Spring Security on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/spring-security/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>