<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>MTLS on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/mtls/</link>
    <description>Recent content in MTLS on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/mtls/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Authenticating Servers with Their Existing Certificates via Traefik mTLS</title>
      <link>https://1shubham7.blog/traefik-mtls-existing-certificates/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/traefik-mtls-existing-certificates/</guid>
      <description>Why the servers I manage authenticate to services in Kubernetes with the certificate their Puppet agent already holds: the Traefik TLSOption and CA Secret, RequireAndVerifyClientCert versus VerifyClientCertIfGiven, the passTLSClientCert header the app reads, and the seven months a stale CA bundle rejected every server without anyone noticing.</description>
    </item>
    
  </channel>
</rss>
