<?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 I was able to resolve this in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-5516x-ssl-cert/m-p/2727198#M171290</link>
    <description>&lt;P&gt;I was able to resolve this issue by following this blog post:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://matthewcevans.com/blog/2015/04/30/cisco-asa-firewall-presents-only-asa-temporary-self-signed-certificate/&lt;/P&gt;</description>
    <pubDate>Thu, 22 Oct 2015 13:24:09 GMT</pubDate>
    <dc:creator>spencermoore</dc:creator>
    <dc:date>2015-10-22T13:24:09Z</dc:date>
    <item>
      <title>ASA 5516x SSL Cert</title>
      <link>https://community.cisco.com/t5/network-security/asa-5516x-ssl-cert/m-p/2727197#M171289</link>
      <description>&lt;P&gt;I recently replaced an ASA 5510 with a new 5516x. I was able to successfully migrate the SSL identity certificate (using the "crypto/import ca export pcks12" command) to the new unit. I also installed the intermediate certificate. When I navigate to the WebVPN page the ASA continues to send a self-signed cert instead of the signed cert I installed which is prompting me to "accept the risk" etc. This is also occurring when I connect using the AnyConnect client. I have selected this cert in the SSL configuration, but it continues to offer the self-signed instead.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your time.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 06:47:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5516x-ssl-cert/m-p/2727197#M171289</guid>
      <dc:creator>spencermoore</dc:creator>
      <dc:date>2019-03-12T06:47:04Z</dc:date>
    </item>
    <item>
      <title>I was able to resolve this</title>
      <link>https://community.cisco.com/t5/network-security/asa-5516x-ssl-cert/m-p/2727198#M171290</link>
      <description>&lt;P&gt;I was able to resolve this issue by following this blog post:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;http://matthewcevans.com/blog/2015/04/30/cisco-asa-firewall-presents-only-asa-temporary-self-signed-certificate/&lt;/P&gt;</description>
      <pubDate>Thu, 22 Oct 2015 13:24:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-5516x-ssl-cert/m-p/2727198#M171290</guid>
      <dc:creator>spencermoore</dc:creator>
      <dc:date>2015-10-22T13:24:09Z</dc:date>
    </item>
  </channel>
</rss>

