<?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 Android BYOD with NSA 2.0.0.64 failures in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4007755#M454682</link>
    <description>&lt;P&gt;Looking to see if anyone else is seeing a similar issue to the one that my client has.&amp;nbsp; I already have a TAC case open. In 8 hours they've made no progress but claim that no one else is reporting this issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They're doing Dual-SSID BYOD with SCEP for certificates, and onboard through ISE using native supplicant provisioning.&amp;nbsp; Windows and Apple are working fine.&amp;nbsp; We had both Android 9 and 10 working using the Network Setup assistant 2.0.0.55.&amp;nbsp; On December 21st Cisco updated the application to 2.0.0.64.&amp;nbsp; Since that update has been pushed all on-boarding for at least Android 9 and 10 has broken.&amp;nbsp; They get to the point where you download the certificates to the Phone and the app errors out with "Certificate Generation Failed".&amp;nbsp; I'm able to load NSA 2.0.0.55 back on an android device and try to on-board, the whole process works as expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm aware that this is the same error that you get when you don't allow EST through, but that appears to only apply to Single SSID onboarding.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have Dual SSID onboarding working with Android currently? I'd love to chat.&lt;/P&gt;</description>
    <pubDate>Tue, 07 Jan 2020 18:01:48 GMT</pubDate>
    <dc:creator>CarlCarlson1234</dc:creator>
    <dc:date>2020-01-07T18:01:48Z</dc:date>
    <item>
      <title>Android BYOD with NSA 2.0.0.64 failures</title>
      <link>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4007755#M454682</link>
      <description>&lt;P&gt;Looking to see if anyone else is seeing a similar issue to the one that my client has.&amp;nbsp; I already have a TAC case open. In 8 hours they've made no progress but claim that no one else is reporting this issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They're doing Dual-SSID BYOD with SCEP for certificates, and onboard through ISE using native supplicant provisioning.&amp;nbsp; Windows and Apple are working fine.&amp;nbsp; We had both Android 9 and 10 working using the Network Setup assistant 2.0.0.55.&amp;nbsp; On December 21st Cisco updated the application to 2.0.0.64.&amp;nbsp; Since that update has been pushed all on-boarding for at least Android 9 and 10 has broken.&amp;nbsp; They get to the point where you download the certificates to the Phone and the app errors out with "Certificate Generation Failed".&amp;nbsp; I'm able to load NSA 2.0.0.55 back on an android device and try to on-board, the whole process works as expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm aware that this is the same error that you get when you don't allow EST through, but that appears to only apply to Single SSID onboarding.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does anyone have Dual SSID onboarding working with Android currently? I'd love to chat.&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jan 2020 18:01:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4007755#M454682</guid>
      <dc:creator>CarlCarlson1234</dc:creator>
      <dc:date>2020-01-07T18:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: Android BYOD with NSA 2.0.0.64 failures</title>
      <link>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4008348#M454685</link>
      <description>&lt;P&gt;Cisco posted a bug for this,&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs60294" target="_self"&gt;CSCvs60294&lt;/A&gt;.&amp;nbsp; It would appear that NSA 2.0.0.64 does not play well with SCEP.&amp;nbsp; &amp;nbsp;Currently no fix other than to use a now unpublished version of NSA.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jan 2020 19:21:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4008348#M454685</guid>
      <dc:creator>CarlCarlson1234</dc:creator>
      <dc:date>2020-01-08T19:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Android BYOD with NSA 2.0.0.64 failures</title>
      <link>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4012971#M454687</link>
      <description>&lt;P&gt;I see 2.0.0.66 available at Google Play store to address this issue.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jan 2020 20:21:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/android-byod-with-nsa-2-0-0-64-failures/m-p/4012971#M454687</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2020-01-16T20:21:38Z</dc:date>
    </item>
  </channel>
</rss>

