<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Signatures on Atlas</title><link>https://www.javiercd.es/en/tags/signatures/</link><description>Recent content in Signatures 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/signatures/index.xml" rel="self" type="application/rss+xml"/><item><title>HMAC Auth in Kong</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/12-autenticacion-hmac-auth/12-autenticacion-hmac-auth/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/12-autenticacion-hmac-auth/12-autenticacion-hmac-auth/</guid><description>&lt;p&gt;HMAC Authentication proves that a request was created by a client that knows a shared secret without sending that secret in the request. In addition to authenticating the client, the signature detects changes to the signed elements while they are in transit.&lt;/p&gt;
&lt;p&gt;This article explains how an HMAC signature is built and validated by Kong Gateway, and how the Consumer relates to its credential. We then build a reproducible Kong Ingress Controller lab and protect &lt;code&gt;/hmac-auth&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>