Why does using CA Import cause the Roots Tree to not display the chain correctly?

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

Why does using CA Import cause the Roots Tree to not display the chain correctly?

L3 Networker
Backstory:Our organization only had production Venafi servers. To better conduct testing, I created a dev/test server and installed a new instance of TPP with its own DB. Also since I was not involved in the setup of the production environment, I figured this would give me a better understanding of how to setup Venafi from scratch.Specifics:I setup the management type in the Policy tree to Unassigned since I would be importing certificates, but did not want to manage them in our dev/test environment. I created a new Job to use CA Import using ourinternal Microsoft Issuing CA. The import of the certificates from the CA was successful, but when I go into the Roots tree it shows my Root CA correctly, but the Issuing CA is under the No Root of Chain Available folder. Not sure what may have caused this. I was wondering if anyone has seen this or has an idea of how to correct it. I will continue to look through the documentation, but there is a lot, so I figured I might get an answer faster here..
0 REPLIES 0
  • 23 Views
  • 0 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!