<?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: Profiling based on Browser Agent in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604513#M528612</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe your custom login web page is external to ISE and not considered as one of ISE guest web portals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ISE web portals are internal to ISE and they have intel on the MAC address along with the User-Agent string so they are able to add the attribute for the endpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For external web access, we rely on HTTP probe and the web access needs to be in clear (non-HTTPS).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Jul 2017 21:11:44 GMT</pubDate>
    <dc:creator>hslai</dc:creator>
    <dc:date>2017-07-10T21:11:44Z</dc:date>
    <item>
      <title>Profiling based on Browser Agent</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604512#M528611</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created a custom login web page that is displayed when certain type of devices join the wifi network.&lt;/P&gt;&lt;P&gt;All works fine but the browser agent of these devices is not detected when hitting this page.&lt;/P&gt;&lt;P&gt;(It is detected for example when hitting the built in guest portal)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I assume the browser agent is saved in some variable in the page code and needs to be sent somewhere internally or something else which I didnt included in my portal code.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can someone explain what should i do for this to work?&lt;/P&gt;&lt;P&gt;Let me know if this is clear or additional explanation is needed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;laszlo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jul 2017 13:24:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604512#M528611</guid>
      <dc:creator>laposilaszlo</dc:creator>
      <dc:date>2017-07-10T13:24:07Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling based on Browser Agent</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604513#M528612</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I believe your custom login web page is external to ISE and not considered as one of ISE guest web portals.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ISE web portals are internal to ISE and they have intel on the MAC address along with the User-Agent string so they are able to add the attribute for the endpoints.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For external web access, we rely on HTTP probe and the web access needs to be in clear (non-HTTPS).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Jul 2017 21:11:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604513#M528612</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2017-07-10T21:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling based on Browser Agent</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604514#M528613</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In our case HTTP profiling is not enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But i made some test in the lab, same setup with HTTP profiling enabled and still user agent is not detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So for example a client joins and in the browser the custom external webpage is shown.&lt;/P&gt;&lt;P&gt;But in ISE this endpoint is shown to be profiled using radius profile and the decision was made based on MAC oui.&lt;/P&gt;&lt;P&gt;No browser agent is detected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Laszlo&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2017 06:56:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604514#M528613</guid>
      <dc:creator>laposilaszlo</dc:creator>
      <dc:date>2017-07-11T06:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: Profiling based on Browser Agent</title>
      <link>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604515#M528614</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You won't get the user-agent from the endpoint unless it is redirected to a portal hosted on ISE or you use Device Sensor on the WLC with HTTP profiling enabled for the SSID.&amp;nbsp; ISE will profile the endpoint to the extent that is has information sent to it like the MAC address, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Tim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jul 2017 14:08:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/profiling-based-on-browser-agent/m-p/3604515#M528614</guid>
      <dc:creator>Timothy Abbott</dc:creator>
      <dc:date>2017-07-11T14:08:53Z</dc:date>
    </item>
  </channel>
</rss>

