<?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 ASDM, Certificate Validation Failuer in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085069#M395486</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not only the clock that has to be in sync. To connect to the ASDM without a certificate-warning you also have to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Use the FQDN or IP that is in the certificate&lt;/P&gt;&lt;P&gt;- Trust that certificate. If it is self-signed then import it into the trusted root store, If it is from your CA, then import the root-cert into your trusted root-store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To investigate that further, please show the output of "show crypto ca certificate".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Nov 2012 10:06:18 GMT</pubDate>
    <dc:creator>Karsten Iwen</dc:creator>
    <dc:date>2012-11-16T10:06:18Z</dc:date>
    <item>
      <title>ASDM, Certificate Validation Failuer</title>
      <link>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085068#M395485</link>
      <description>&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to access my firewall using ASDM but it is giving me an error 'Certificate Validation Failure'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have manually set a clock on the firewall to match with the machine from where I am trying to access FW using ASDM&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA version is 8.2 (2) &amp;amp; ASDM version is 7.0&lt;/P&gt;&lt;P&gt;I get same error message with ASDM 6.4&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:24:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085068#M395485</guid>
      <dc:creator>central_bank</dc:creator>
      <dc:date>2019-03-12T00:24:18Z</dc:date>
    </item>
    <item>
      <title>ASDM, Certificate Validation Failuer</title>
      <link>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085069#M395486</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not only the clock that has to be in sync. To connect to the ASDM without a certificate-warning you also have to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Use the FQDN or IP that is in the certificate&lt;/P&gt;&lt;P&gt;- Trust that certificate. If it is self-signed then import it into the trusted root store, If it is from your CA, then import the root-cert into your trusted root-store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To investigate that further, please show the output of "show crypto ca certificate".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2012 10:06:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085069#M395486</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2012-11-16T10:06:18Z</dc:date>
    </item>
    <item>
      <title>ASDM, Certificate Validation Failuer</title>
      <link>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085070#M395487</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; The output of sh crypto ca certificate is blank.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2012 10:41:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085070#M395487</guid>
      <dc:creator>central_bank</dc:creator>
      <dc:date>2012-11-16T10:41:40Z</dc:date>
    </item>
    <item>
      <title>ASDM, Certificate Validation Failuer</title>
      <link>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085071#M395488</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The easiest way to get ASDM-Access should be with the setup-command. Accept everything that is preconfigured correctly and add all that is missing (i.g. the host that runs the ASDM).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&amp;nbsp; &lt;BR /&gt;Don't stop after you've improved your network! Improve the world by lending money to the working poor: &lt;BR /&gt;&lt;A class="jive-link-external-small" href="http://www.kiva.org/invitedby/karsteni"&gt;http://www.kiva.org/invitedby/karsteni&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Nov 2012 10:51:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-certificate-validation-failuer/m-p/2085071#M395488</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2012-11-16T10:51:47Z</dc:date>
    </item>
  </channel>
</rss>

