<?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 Atlas</title><link>https://www.javiercd.es/en/tags/jwt/</link><description>Recent content in JWT on Atlas</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://www.javiercd.es/en/tags/jwt/index.xml" rel="self" type="application/rss+xml"/><item><title>JWT Auth in Kong</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/13-autenticacion-jwt/13-autenticacion-jwt/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/13-autenticacion-jwt/13-autenticacion-jwt/</guid><description>&lt;p&gt;A JSON Web Token carries claims about an identity inside a signed token. Kong can verify its signature and time constraints before the request reaches the backend.&lt;/p&gt;
&lt;p&gt;This article separates the token structure, the cryptographic credential stored in Kong, and the Consumer representing the client. We then build a reproducible Kong Ingress Controller lab with an HS256-signed JWT and a &lt;code&gt;/jwt&lt;/code&gt; route.&lt;/p&gt;
&lt;div class="alert info"&gt;
&lt;span&gt;&lt;i data-feather="info"&gt;&lt;/i&gt;&lt;/span&gt;
&lt;span&gt;&lt;strong&gt;&lt;p&gt;This lab continues directly from &lt;a href="https://www.javiercd.es/posts/kong/03-instalacion-kic/03-instalacion-kic/"&gt;Installing KIC&lt;/a&gt;. It reuses the &lt;code&gt;kong&lt;/code&gt; Gateway, the &lt;code&gt;echo&lt;/code&gt; Service, and the &lt;code&gt;192.168.121.200&lt;/code&gt; address assigned by MetalLB to &lt;code&gt;kong-gateway-proxy&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>