<?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 Certain Android device does not get custom CWA page in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494005#M73613</link>
    <description>&lt;P&gt;On my Guest SSID, I have a custom CWA page. It works for everyone except for one Android device.&lt;/P&gt;&lt;P&gt;I see the device meet the criteria to hit a certain authorization profile, one that I know has a CWA action of hitting my custom page. This is the same rule all other guests hit. Except, instead of going to the custom page, this device goes to the Cisco default portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is very odd. All log entries look correct, but what the user is seeing is not. The device matches the profile 'Android-Samsung'.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 04:55:39 GMT</pubDate>
    <dc:creator>Josh Morris</dc:creator>
    <dc:date>2019-03-11T04:55:39Z</dc:date>
    <item>
      <title>Certain Android device does not get custom CWA page</title>
      <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494005#M73613</link>
      <description>&lt;P&gt;On my Guest SSID, I have a custom CWA page. It works for everyone except for one Android device.&lt;/P&gt;&lt;P&gt;I see the device meet the criteria to hit a certain authorization profile, one that I know has a CWA action of hitting my custom page. This is the same rule all other guests hit. Except, instead of going to the custom page, this device goes to the Cisco default portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is very odd. All log entries look correct, but what the user is seeing is not. The device matches the profile 'Android-Samsung'.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 04:55:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494005#M73613</guid>
      <dc:creator>Josh Morris</dc:creator>
      <dc:date>2019-03-11T04:55:39Z</dc:date>
    </item>
    <item>
      <title>Can you confirm if the device</title>
      <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494006#M73614</link>
      <description>&lt;P&gt;Can you confirm if the device is hitting your authorization rule or is it hitting the default one?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Aug 2014 00:21:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494006#M73614</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2014-08-08T00:21:12Z</dc:date>
    </item>
    <item>
      <title>Android devices need to be</title>
      <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494007#M73615</link>
      <description>&lt;P&gt;Android devices need to be treated differently than iOS Devices and/or Windows. This is partially because no two Android devices are exactly the same, but also because of the requirement to use a supplicant provisioning App to configure the Supplicant and Certificate for Android.&lt;/P&gt;&lt;P&gt;Please recheck the config:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/design-zone-security/howto_61_byod_provisioning.pdf"&gt;http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/design-zone-security/howto_61_byod_provisioning.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Aug 2014 08:59:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494007#M73615</guid>
      <dc:creator>mohanak</dc:creator>
      <dc:date>2014-08-08T08:59:51Z</dc:date>
    </item>
    <item>
      <title>I have confirmed it is</title>
      <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494008#M73616</link>
      <description>&lt;P&gt;I have confirmed it is hitting the right authorization rule. My web-auth redirection rule is simple...&lt;/P&gt;&lt;P&gt;If the client is Wireless MAB AND it is coming from WLAN ID 12, then redirect to CWA.&lt;/P&gt;&lt;P&gt;My default rule is actually DenyAccss, and there is no other rule for CWA. It's just like this one device&amp;nbsp;can't process the custom webauth page.&lt;/P&gt;</description>
      <pubDate>Fri, 08 Aug 2014 13:07:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494008#M73616</guid>
      <dc:creator>Josh Morris</dc:creator>
      <dc:date>2014-08-08T13:07:56Z</dc:date>
    </item>
    <item>
      <title>Hmm that is interesting.</title>
      <link>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494009#M73617</link>
      <description>&lt;P&gt;Hmm that is interesting. Haven't ran into this problem before. I wonder if something in the Andorid browser is being cached. When you open the browser do you at least see the device trying to go to the redirect URL?&lt;/P&gt;&lt;P&gt;Can you also post screen shots of your AAA policies in ISE&lt;/P&gt;</description>
      <pubDate>Fri, 08 Aug 2014 20:17:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/certain-android-device-does-not-get-custom-cwa-page/m-p/2494009#M73617</guid>
      <dc:creator>nspasov</dc:creator>
      <dc:date>2014-08-08T20:17:26Z</dc:date>
    </item>
  </channel>
</rss>

