<?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: ISE BYOD MAC onboarding in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836982#M473973</link>
    <description>I don’t understand why you would think about doing this.&lt;BR /&gt;&lt;BR /&gt;If you’re using dot1x you’re using some sort of saved credentials. Either cert of username/password. You need these for proper authentication, otherwise it won’t work.&lt;BR /&gt;&lt;BR /&gt;MAB is used on open networks or perhaps even WPA-PSK and can register a device into an endpoint group&lt;BR /&gt;see cisco live  - &lt;A href="https://www.ciscolive.com/global/on-demand-library.html?search=federico%20z%20barcelona#/session/1532112828591001teh9" target="_blank"&gt;https://www.ciscolive.com/global/on-demand-library.html?search=federico%20z%20barcelona#/session/1532112828591001teh9&lt;/A&gt;&lt;BR /&gt;guest design guide under &lt;A href="http://cs.co/ise-guest" target="_blank"&gt;http://cs.co/ise-guest&lt;/A&gt; and &lt;A href="http://cs.co/ise-byod" target="_blank"&gt;http://cs.co/ise-byod&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 11 Apr 2019 16:30:33 GMT</pubDate>
    <dc:creator>Jason Kunst</dc:creator>
    <dc:date>2019-04-11T16:30:33Z</dc:date>
    <item>
      <title>ISE BYOD MAC onboarding</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836332#M473968</link>
      <description>&lt;P&gt;for BYOD, can we USE MAC Address instead of Cert ?&lt;/P&gt;&lt;P&gt;we have Customer with ISE 2.4, does not wants to use cert onboarding and wants to keep mac address without adding?&lt;/P&gt;&lt;P&gt;Flow should be like This.&amp;nbsp;&lt;/P&gt;&lt;P&gt;end devices connect to BYOD&amp;nbsp;SSID, then ask for ad user/password. then ISE keep mac and next time ISE should not ask user/password. and next time use mac for authentication.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Customer does not want to add mac manually. after first time login with AD username/password. ise&amp;nbsp;should Keep its mac for certain period.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 20:57:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836332#M473968</guid>
      <dc:creator>azhar_eaggle1</dc:creator>
      <dc:date>2019-04-10T20:57:28Z</dc:date>
    </item>
    <item>
      <title>Re: ISE BYOD MAC onboarding</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836452#M473969</link>
      <description>&lt;P&gt;This is just standard sponsored guest portal setup.&amp;nbsp; In the sponsored guest portal you have the options to set a guest type for "Employees using this portal".&amp;nbsp; That guest type is tied to an endpoint identity group.&amp;nbsp; You decide how often to purge that identity group.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So employee connects to the SSID, gets redirected to the portal, enters their AD credentials, optionally accepts an AUP page and then their MAC address is added to the endpoint identity group you specified in the employee guest type.&amp;nbsp; How often you purge the endpoint identity group determines how often the employees have to see the portal.&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2019 02:27:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836452#M473969</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2019-04-11T02:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE BYOD MAC onboarding</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836462#M473971</link>
      <description>I recommend understand the respective prescriptive guides under &lt;A href="http://cs.co/ise-byod" target="_blank"&gt;http://cs.co/ise-byod&lt;/A&gt; and ise-guest&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Apr 2019 02:39:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836462#M473971</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-04-11T02:39:33Z</dc:date>
    </item>
    <item>
      <title>Re: ISE BYOD MAC onboarding</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836982#M473973</link>
      <description>I don’t understand why you would think about doing this.&lt;BR /&gt;&lt;BR /&gt;If you’re using dot1x you’re using some sort of saved credentials. Either cert of username/password. You need these for proper authentication, otherwise it won’t work.&lt;BR /&gt;&lt;BR /&gt;MAB is used on open networks or perhaps even WPA-PSK and can register a device into an endpoint group&lt;BR /&gt;see cisco live  - &lt;A href="https://www.ciscolive.com/global/on-demand-library.html?search=federico%20z%20barcelona#/session/1532112828591001teh9" target="_blank"&gt;https://www.ciscolive.com/global/on-demand-library.html?search=federico%20z%20barcelona#/session/1532112828591001teh9&lt;/A&gt;&lt;BR /&gt;guest design guide under &lt;A href="http://cs.co/ise-guest" target="_blank"&gt;http://cs.co/ise-guest&lt;/A&gt; and &lt;A href="http://cs.co/ise-byod" target="_blank"&gt;http://cs.co/ise-byod&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 11 Apr 2019 16:30:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-byod-mac-onboarding/m-p/3836982#M473973</guid>
      <dc:creator>Jason Kunst</dc:creator>
      <dc:date>2019-04-11T16:30:33Z</dc:date>
    </item>
  </channel>
</rss>

