- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
09-09-2025 10:05 AM
The Sectigo template has 3 certificates to build the chain from. When we sign an external certificate it shows the 'Sectigo Public Server Authentication Root R46' as the root certificate instead of showing the 'USERTest RSA Certification Authority' as the root. I've added screenshots of the template cert container and a cert chain from a signed cert.
09-15-2025 06:50 AM
You are looking for the cross-signed Sectigo certificate chain that chains back to the legacy root CA instead of the new chain to the new Root CA. In the CA template in the Policy Tree you can chose "Certificate Chain Preferences" and specify which chain you want to include with your Sectigo certificates. Just beware that this might throw an error as its doing so for me in my prod environment but not my non-prod. I have a ticket open to investigate. Also, this assumes you are running 25.1 with the updated REST API integration to Sectigo.
09-15-2025 06:52 AM
Also, this chain is only necessary if you have applications that do not trust the R46 root. This root has been in public trust stores since 2023 so the majority of applications should trust it as long as they are updated regularly.
09-15-2025 07:33 AM
Hi Shawn - We are using version 24.1 so there is no 'Certificate Chain Preferences' tab on the CA template... just 'Certificates'. That is the first screenshot Maxx shared above showing the chain we want to use:
We've run into some issues using the newer root certs on some of our public sites (customers using older iphones or ipads that haven't been updated in a few years) which is why we want to use that older root cert.
09-16-2025 01:29 AM
Ah, okay. It doesn't matter what is shown in Venafi. If you have the trust chain built this way when you download a certificate from Venafi (or provision automatically via an installation) it will provision the chain as you have specified. I would advise you to download the above certificate via the Aperture interface and inspect what chain is included.
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!

