<?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 Re: Cannot Import HTTPS Certificate into FMC - SAN attribute in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262549#M1076861</link>
    <description>&lt;P&gt;When you generate a CSR using a tool such as I suggested you have complete control over which fields are included (SAN, CN etc.). That way you can include both the SAN that your CA requires as well as the CN which FMC requires.&lt;/P&gt;</description>
    <pubDate>Tue, 22 Dec 2020 18:08:49 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2020-12-22T18:08:49Z</dc:date>
    <item>
      <title>Cannot Import HTTPS Certificate into FMC - SAN attribute</title>
      <link>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262474#M1076852</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm using Cisco Firepower Management Center 1000 version 6.3.0.2. I tried to renew the HTTPS-Certificate under System -&amp;gt; Configuration -&amp;gt; HTTPS Certificate. I generated new certificate our CA and later I tried to import the new certificate. But I got an error (Invalid certificate).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;My CA requires a SAN attribute, but the CNAME attribute is optional. CSR's FMC out-of-the-box not supported SAN attribute . Is there a solution to this problem?&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 16:19:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262474#M1076852</guid>
      <dc:creator>AlexanderD</dc:creator>
      <dc:date>2020-12-22T16:19:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Import HTTPS Certificate into FMC - SAN attribute</title>
      <link>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262483#M1076853</link>
      <description>&lt;P&gt;Create your CSR separately from FMC using openssl or something like XCA (Windows freeware). Submit it to the CA and get the signed certificate. Then import the signed certificate and private key into FMC.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 16:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262483#M1076853</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-12-22T16:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Import HTTPS Certificate into FMC - SAN attribute</title>
      <link>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262528#M1076859</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have already issued the certificate directly on our&amp;nbsp; CA (Unipass). I tried to import the separately keys (public, private, chain) without success. What's the advantage of creating CSR using openssl versus importing a &lt;SPAN&gt;signed certificate&lt;/SPAN&gt;?&lt;/P&gt;&lt;P&gt;Our CA not supported other templates.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 17:42:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262528#M1076859</guid>
      <dc:creator>AlexanderD</dc:creator>
      <dc:date>2020-12-22T17:42:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot Import HTTPS Certificate into FMC - SAN attribute</title>
      <link>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262549#M1076861</link>
      <description>&lt;P&gt;When you generate a CSR using a tool such as I suggested you have complete control over which fields are included (SAN, CN etc.). That way you can include both the SAN that your CA requires as well as the CN which FMC requires.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Dec 2020 18:08:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-import-https-certificate-into-fmc-san-attribute/m-p/4262549#M1076861</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-12-22T18:08:49Z</dc:date>
    </item>
  </channel>
</rss>

