<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Istio - Tag - azuar4e</title><link>https://azuar4e.github.io/en/tags/istio/</link><description>azuar4e</description><generator>Hugo 0.147.8 &amp; FixIt v0.3.21-b2e6f70a</generator><language>en</language><managingEditor>azuar4e@gmail.com (Angel Azuara Eizaguirre)</managingEditor><webMaster>azuar4e@gmail.com (Angel Azuara Eizaguirre)</webMaster><lastBuildDate>Mon, 08 Jun 2026 20:43:48 +0200</lastBuildDate><atom:link href="https://azuar4e.github.io/en/tags/istio/index.xml" rel="self" type="application/rss+xml"/><item><title>Zero Trust on Kubernetes: Securing Microservices with Istio mTLS and Keycloak</title><link>https://azuar4e.github.io/en/posts/micros-sec-istio/</link><pubDate>Mon, 08 Jun 2026 20:43:48 +0200</pubDate><author>azuar4e@gmail.com (Angel Azuara Eizaguirre)</author><guid>https://azuar4e.github.io/en/posts/micros-sec-istio/</guid><category domain="https://azuar4e.github.io/en/categories/personal-projects/">Personal Projects</category><description>&lt;p>Have you ever wondered how to handle user authentication by delegating it to an &lt;em>Identity Provider&lt;/em> (IdP), and how to secure communication between your microservices without having to implement that logic yourself? That&amp;rsquo;s exactly what we&amp;rsquo;re going to look at in this article.&lt;/p>
&lt;p>The motivation for this post comes from the need to address some of the limitations of my &lt;a href="https://azuar4e.github.io/es/posts/tfg/"target="_blank" rel="external nofollow noopener noreferrer">bachelor&amp;rsquo;s thesis&lt;/a>. The two main shortcomings were user authentication, which was handled manually by generating a JWT, and the lack of HTTPS in communication between microservices. In this new project we solve both: we delegate authentication to a real IdP, and we secure internal communications with mTLS transparently at the application level.&lt;/p></description></item></channel></rss>