<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Technical Blog on David Picillo - Cloud DevOps Engineer</title><link>https://www.picillo.de/en/blog/</link><description>Recent content in Technical Blog on David Picillo - Cloud DevOps Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 11 May 2026 01:58:35 +0200</lastBuildDate><atom:link href="https://www.picillo.de/en/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Keycloak in Front of Active Directory: User Federation, MFA, and Common Pitfalls</title><link>https://www.picillo.de/en/blog/keycloak-active-directory/</link><pubDate>Wed, 15 Jan 2025 10:00:00 +0000</pubDate><guid>https://www.picillo.de/en/blog/keycloak-active-directory/</guid><description>&lt;h2 id="what-this-is-about"&gt;What this is about&lt;/h2&gt;
&lt;p&gt;In most enterprises, the truth about identities still lives in Active Directory. Meanwhile, modern applications have long since standardized on OIDC or SAML — protocols that AD doesn&amp;rsquo;t natively offer. Maintaining two user stores isn&amp;rsquo;t an option. This is where &lt;strong&gt;Keycloak in front of AD&lt;/strong&gt; comes in: Keycloak federates against the existing AD, takes over the role of Identity Provider, adds MFA, and delivers the protocol coverage that AD alone will never provide.&lt;/p&gt;</description></item></channel></rss>