<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>LDAP Auth in Kong Gateway on Atlas</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/18-autenticacion-ldap/</link><description>Recent content in LDAP 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/18-autenticacion-ldap/index.xml" rel="self" type="application/rss+xml"/><item><title>LDAP Auth in Kong</title><link>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/18-autenticacion-ldap/18-autenticacion-ldap/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0200</pubDate><guid>https://www.javiercd.es/en/posts/kong/plugins-autenticacion/18-autenticacion-ldap/18-autenticacion-ldap/</guid><description>&lt;p&gt;LDAP Authentication lets Kong validate a username and password directly against a corporate directory. The backend does not receive those credentials and does not need to implement LDAP.&lt;/p&gt;
&lt;p&gt;This article explains how the authentication header is built, how Kong locates the user in the directory, and how to protect &lt;code&gt;/ldap-auth&lt;/code&gt; through Kong Ingress Controller.&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 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>