<?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 Why does using CA Import cause the Roots Tree to not display the chain correctly? in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-using-ca-import-cause-the-roots-tree-to-not-display-the/m-p/1336576#M143</link>
    <description>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..</description>
    <pubDate>Wed, 11 Jan 2023 19:14:48 GMT</pubDate>
    <dc:creator>dghort</dc:creator>
    <dc:date>2023-01-11T19:14:48Z</dc:date>
    <item>
      <title>Why does using CA Import cause the Roots Tree to not display the chain correctly?</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-using-ca-import-cause-the-roots-tree-to-not-display-the/m-p/1336576#M143</link>
      <description>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..</description>
      <pubDate>Wed, 11 Jan 2023 19:14:48 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/why-does-using-ca-import-cause-the-roots-tree-to-not-display-the/m-p/1336576#M143</guid>
      <dc:creator>dghort</dc:creator>
      <dc:date>2023-01-11T19:14:48Z</dc:date>
    </item>
  </channel>
</rss>

