<?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: Client behavior with dot1x connecting to ISE requires user to accept certificate in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496515#M511236</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you use an MDM to manage these mobile devices and push out the SSID and trust certs they shouldn't see the cert warning.&amp;nbsp; I am guessing these aren't managed devices though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 28 Mar 2018 13:20:10 GMT</pubDate>
    <dc:creator>paul</dc:creator>
    <dc:date>2018-03-28T13:20:10Z</dc:date>
    <item>
      <title>Client behavior with dot1x connecting to ISE requires user to accept certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496513#M511233</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Our scenario here when a mobile device IOS/Android connect to our wireless first time they need to accept the Trust certificate.&lt;/P&gt;&lt;P&gt;Is there a way to disable the issue of certificate to a particular SSID but the device still login using 802.x?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ruel&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2018 08:13:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496513#M511233</guid>
      <dc:creator>rhuel.phils</dc:creator>
      <dc:date>2018-03-28T08:13:18Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Certificate disable</title>
      <link>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496514#M511235</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;iOS devices will allows require you to manually trust a certificate for the first connection  (even if it’s well known), this is apples decision, the only way around that is to push a profile to it (via BYOD process on ISE or mdm enrollment) this kinda defeats the purpose of easy connection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I haven’t played around with Android in a while&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can not disable it, it’s part of dot1x communication to trust the certificate presented from the AAA server&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also when roaming to another ISE psn the user would have to do this again unless you have deployed a well known certificate with a wildcard in the SAN or a certificate with all of the ISE psn names prepopulated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is some good reading on the matter&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;https://www.networkworld.com/article/2225032/infrastructure-management/what-are-wildcard-certificates-and-how-do-i-use-them-with-ciscos-ise.html&lt;/P&gt;&lt;P&gt;&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#ID121&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2018 12:11:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496514#M511235</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2018-03-28T12:11:25Z</dc:date>
    </item>
    <item>
      <title>Re: Client behavior with dot1x connecting to ISE requires user to accept certificate</title>
      <link>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496515#M511236</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you use an MDM to manage these mobile devices and push out the SSID and trust certs they shouldn't see the cert warning.&amp;nbsp; I am guessing these aren't managed devices though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 28 Mar 2018 13:20:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/client-behavior-with-dot1x-connecting-to-ise-requires-user-to/m-p/3496515#M511236</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-03-28T13:20:10Z</dc:date>
    </item>
  </channel>
</rss>

