<?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: How To: Implement ISE Server-Side Certificates document in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549151#M520388</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct on this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 27 Oct 2017 01:02:09 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-10-27T01:02:09Z</dc:date>
    <item>
      <title>How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549146#M520383</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Forum,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this document (page 14) where u use the same cert on all PSN's.... I'm planning to use the same cert on all PSN's only for EAP authentication. CN in the cert will be something like aaa.company.localdomain&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;my questions:&lt;/P&gt;&lt;P&gt;Don't the hostname of every PSN has to be aaa.company.localdomain ??otherwise the hostname won't match the CN and client supplicant would reject the cert??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;let me know.&lt;/P&gt;&lt;P&gt;thanks,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 20:54:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549146#M520383</guid>
      <dc:creator>ffadhilpi</dc:creator>
      <dc:date>2017-10-26T20:54:06Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549147#M520384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check this out&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;https://www.cisco.com/c/en/us/td/docs/security/ise/2-3/admin_guide/b_ise_admin_guide_23/b_ise_admin_guide_23_chapter_0111.html#concept_8ECCCAF1252E40DDB9A786C0AC7BC3B2&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 22:04:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549147#M520384</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-10-26T22:04:10Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549148#M520385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;are you trying to point wild card certs?&lt;/P&gt;&lt;P&gt;Windows machines don't support RADIUS auth to a wild card cert!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 22:44:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549148#M520385</guid>
      <dc:creator>ffadhilpi</dc:creator>
      <dc:date>2017-10-26T22:44:12Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549149#M520386</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, Actually they do, a wildcard in the SAN, it’s shown on the admin guide page&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Otherwise you would need to have one cert with the following&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Each host will resolve to the SAN name&lt;/P&gt;&lt;P&gt;CN aaa.domain.local&lt;/P&gt;&lt;P&gt;San aaa.domain.local&lt;/P&gt;&lt;P&gt;Then every host psn name&lt;/P&gt;&lt;P&gt;Psn1.domain.com&amp;lt;http://Psn1.domain.com&amp;gt;&lt;/P&gt;&lt;P&gt;PSN2.&lt;/P&gt;&lt;P&gt;Psn3&lt;/P&gt;&lt;P&gt;Sponsor.domain.com&amp;lt;http://Sponsor.domain.com&amp;gt;&lt;/P&gt;&lt;P&gt;Mydevices.domain.com&amp;lt;http://Mydevices.domain.com&amp;gt;&lt;/P&gt;&lt;P&gt;Etc&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This works ok if your hosts are static but if you wanted to add more psn or other services later then you would need to purchase another cert&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 22:58:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549149#M520386</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2017-10-26T22:58:46Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549150#M520387</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think I caused a confusion.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sponsors and portal are our of picture. This is purely for EAP auth.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If the CN is aaa.company.localdomain&lt;/P&gt;&lt;P&gt;and no SAN's (as far as I know SAN is not evaluated in a RADIUS transaction)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;should it matter what the hostname of my PSNs is? as long as the root CA is trusted?!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Oct 2017 23:27:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549150#M520387</guid>
      <dc:creator>ffadhilpi</dc:creator>
      <dc:date>2017-10-26T23:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549151#M520388</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You are correct on this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Oct 2017 01:02:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549151#M520388</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-10-27T01:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: How To: Implement ISE Server-Side Certificates document</title>
      <link>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549152#M520389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;As long as the root, the signing ca cert, is trusted by your Windows supplicant, the CN field of your PEAP cert doesn’t matter. I named my as “psn.xxx.xxx.org”, works fine for all my PSN nodes that share the cert. (note: obviously my PSN nodes have their unique FQDN)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Oct 2017 17:53:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/how-to-implement-ise-server-side-certificates-document/m-p/3549152#M520389</guid>
      <dc:creator>Ping Zhou</dc:creator>
      <dc:date>2017-10-27T17:53:45Z</dc:date>
    </item>
  </channel>
</rss>

