<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Basic Auth on Atlas</title><link>https://www.javiercd.es/en/tags/basic-auth/</link><description>Recent content in Basic Auth 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/basic-auth/index.xml" rel="self" type="application/rss+xml"/><item><title>Basic Auth in Kong</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/10-autenticacion-basic-auth/10-autenticacion-basic-auth/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/10-autenticacion-basic-auth/10-autenticacion-basic-auth/</guid><description>&lt;p&gt;Basic Authentication may seem like a trivial mechanism because it only uses a username and a password. However, using it correctly means separating three ideas: the HTTP standard, the validation performed by Kong Gateway, and the identity that Kong associates with valid credentials.&lt;/p&gt;
&lt;p&gt;In this article we will look at those three layers and build a reproducible lab with Kong Ingress Controller. The goal is not simply to copy files and blindly apply them. First we will understand what each resource represents, then we will apply it, and finally we will check what happens inside Kong.&lt;/p&gt;</description></item></channel></rss>