<?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 Adding to Karsten's correct in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750990#M54430</link>
    <description>&lt;P&gt;Adding to Karsten's correct answer - make sure you have SANs even when using a wildcard certificate. That's because native Windows 802.1x supplicants will not properly trust a wildcard certificate.&lt;/P&gt;&lt;P&gt;If you're only doing Central Web Authentication (CWA) or exclusively deploying the AnyConnect Secure Mobility Client Network Access Module (NAM) as your supplicant it's not a problem.&lt;/P&gt;</description>
    <pubDate>Sun, 16 Aug 2015 14:18:06 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2015-08-16T14:18:06Z</dc:date>
    <item>
      <title>Cisco ise 1.3  subject alternative name SAN</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750988#M54427</link>
      <description>&lt;P&gt;hi, who can help me to understand san on Ise 1.3.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:58:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750988#M54427</guid>
      <dc:creator>Augustgood</dc:creator>
      <dc:date>2019-03-11T05:58:33Z</dc:date>
    </item>
    <item>
      <title>You want to access the</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750989#M54428</link>
      <description>&lt;P&gt;You want to access the webpages of the ISE by different names. A good example for that is the my-devices or the&amp;nbsp;sponsor-portal. To access it by the native name of one of your ISEs would be quite unfriendly to your users. If they can access that asmydevices.example.net and &amp;nbsp;sponsorportal.example.net, it's much easier for the users. But for not getting a cert-warning, you need to have all additional names added to the certificate. These are the "Subject Alternate Names"or SANs. Another method to achieve the same is to use a &lt;A href="http://www.cisco.com/c/en/us/td/docs/security/ise/1-3/admin_guide/b_ise_admin_guide_13/b_ise_admin_guide_sample_chapter_01000.html#concept_8ECCCAF1252E40DDB9A786C0AC7BC3B2"&gt;wildcard-certificate&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Aug 2015 08:25:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750989#M54428</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2015-08-16T08:25:52Z</dc:date>
    </item>
    <item>
      <title>Adding to Karsten's correct</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750990#M54430</link>
      <description>&lt;P&gt;Adding to Karsten's correct answer - make sure you have SANs even when using a wildcard certificate. That's because native Windows 802.1x supplicants will not properly trust a wildcard certificate.&lt;/P&gt;&lt;P&gt;If you're only doing Central Web Authentication (CWA) or exclusively deploying the AnyConnect Secure Mobility Client Network Access Module (NAM) as your supplicant it's not a problem.&lt;/P&gt;</description>
      <pubDate>Sun, 16 Aug 2015 14:18:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-subject-alternative-name-san/m-p/2750990#M54430</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-08-16T14:18:06Z</dc:date>
    </item>
  </channel>
</rss>

