<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why does our deprecated 2027 root CA keep reappearing in certificate chains, even after deletion? We've migrated to a 2040 root, but Venafi keeps pulling the old one back. Anyone seen this before or know what causes it? in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-our-deprecated-2027-root-ca-keep-reappearing-in/m-p/1419379#M486</link>
    <description>&lt;P&gt;check out the doc on cert chaining here: https://docs.venafi.com/Docs/current/TopNav/Content/Drivers/cco-CATemplateObjects-CAChaining-tpp.php&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it says: When building a chain for a certificate, TLS Protect can use three sources of information&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Chains from the CA during enrollment&lt;/LI&gt;&lt;LI&gt;Certificates on the roots tree&lt;/LI&gt;&lt;LI&gt;Windows certificate store&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We had this issue in the past, and solved it by removing it from the machines hosting the &lt;S&gt;Venafi&lt;/S&gt; &lt;S&gt;TPP&lt;/S&gt; TPF services.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Jun 2026 17:27:38 GMT</pubDate>
    <dc:creator>Carl_Mehner</dc:creator>
    <dc:date>2026-06-17T17:27:38Z</dc:date>
    <item>
      <title>Why does our deprecated 2027 root CA keep reappearing in certificate chains, even after deletion? We've migrated to a 2040 root, but Venafi keeps pulling the old one back. Anyone seen this before or know what causes it?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-our-deprecated-2027-root-ca-keep-reappearing-in/m-p/1419378#M485</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We’re facing a strange issue with our certificate chain in Venafi TPP and hoping someone might have insight.&lt;/P&gt;&lt;P&gt;About 7 years ago, we transitioned to a new root CA the current one expires in 2040. The previous root (expiring in 2027) is no longer needed and should not be part of any new certificate chains.&lt;/P&gt;&lt;P&gt;However, despite deleting the 2027 root from Venafi, it keeps reappearing in the chain of newly issued certificates. When we remove it, the correct chain (ending in the 2040 root) shows up as expected but after a day or two, the 2027 root finds its way back into the trust store and starts appearing again.&lt;/P&gt;&lt;P&gt;We’ve checked the CA (Microsoft ADCS) and confirmed that the 2027 root is no longer actively used. We’ve also tried manually defining the certificate chain in the CA template, but the issue persists.&lt;/P&gt;&lt;P&gt;Has anyone experienced something similar? Could there be a sync job, driver behavior, or policy object that’s reintroducing the old root? Any guidance would be appreciated.&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Wed, 08 Oct 2025 05:48:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-our-deprecated-2027-root-ca-keep-reappearing-in/m-p/1419378#M485</guid>
      <dc:creator>AMaseko</dc:creator>
      <dc:date>2025-10-08T05:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Why does our deprecated 2027 root CA keep reappearing in certificate chains, even after deletion? We've migrated to a 2040 root, but Venafi keeps pulling the old one back. Anyone seen this before or know what causes it?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-our-deprecated-2027-root-ca-keep-reappearing-in/m-p/1419379#M486</link>
      <description>&lt;P&gt;check out the doc on cert chaining here: https://docs.venafi.com/Docs/current/TopNav/Content/Drivers/cco-CATemplateObjects-CAChaining-tpp.php&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;it says: When building a chain for a certificate, TLS Protect can use three sources of information&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Chains from the CA during enrollment&lt;/LI&gt;&lt;LI&gt;Certificates on the roots tree&lt;/LI&gt;&lt;LI&gt;Windows certificate store&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We had this issue in the past, and solved it by removing it from the machines hosting the &lt;S&gt;Venafi&lt;/S&gt; &lt;S&gt;TPP&lt;/S&gt; TPF services.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jun 2026 17:27:38 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-our-deprecated-2027-root-ca-keep-reappearing-in/m-p/1419379#M486</guid>
      <dc:creator>Carl_Mehner</dc:creator>
      <dc:date>2026-06-17T17:27:38Z</dc:date>
    </item>
  </channel>
</rss>

