<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Authentication on Antonio Montemurro</title><link>https://antoniomontemurro.com/en/tags/authentication/</link><description>Recent content in Authentication on Antonio Montemurro</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 13 Oct 2024 15:25:28 +0000</lastBuildDate><atom:link href="https://antoniomontemurro.com/en/tags/authentication/index.xml" rel="self" type="application/rss+xml"/><item><title>JWT Authentication</title><link>https://antoniomontemurro.com/en/posts/jwt-authentication/</link><pubDate>Sun, 13 Oct 2024 15:25:28 +0000</pubDate><guid>https://antoniomontemurro.com/en/posts/jwt-authentication/</guid><description>&lt;p&gt;Have you ever noticed that some websites have a private section that requires a username and password to access? You might also have noticed that, once logged in, you’re often not asked to re-enter your username and password for subsequent visits. In stateless web applications, this behavior is achievable by using a JWT token. JWT, which stands for JSON Web Token, is a data exchange standard defined by RFC7519 in 2015.&lt;/p&gt;</description></item></channel></rss>