<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Key Auth in Kong Gateway on Atlas</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/11-autenticacion-key-auth/</link><description>Recent content in Key Auth in Kong Gateway 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/posts/kong/plugins-autenticacion/11-autenticacion-key-auth/index.xml" rel="self" type="application/rss+xml"/><item><title>Key Auth in Kong</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/11-autenticacion-key-auth/11-autenticacion-key-auth/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/11-autenticacion-key-auth/11-autenticacion-key-auth/</guid><description>&lt;p&gt;An API key may look like little more than a random string that a client adds to every request. To use it correctly, however, it helps to separate three ideas: the credential presented by the client, the validation performed by Kong Gateway, and the identity of the Consumer associated with that credential.&lt;/p&gt;
&lt;p&gt;This article covers those three layers and builds a reproducible lab with Kong Ingress Controller. We will first understand each resource, then apply it, and finally verify what happens inside Kong.&lt;/p&gt;</description></item></channel></rss>