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?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

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?

L1 Bithead

Hi

We’re facing a strange issue with our certificate chain in Venafi TPP and hoping someone might have insight.

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.

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.

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.

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.

Thanks in advance

1 REPLY 1

L0 Member

check out the doc on cert chaining here: https://docs.venafi.com/Docs/current/TopNav/Content/Drivers/cco-CATemplateObjects-CAChaining-tpp.php

 

it says: When building a chain for a certificate, TLS Protect can use three sources of information

  • Chains from the CA during enrollment
  • Certificates on the roots tree
  • Windows certificate store

We had this issue in the past, and solved it by removing it from the machines hosting the Venafi TPP TPF services.

  • 111 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!