<?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: why byod provisioning in Cloudpath Enrollment System (ES)</title>
    <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8130#M24</link>
    <description>This is the powerfull feature. For example you want create ssid for Employee(integrate with Active Directory) &amp;amp; Guest on 1 onboarding portal. The step is create:&lt;BR /&gt;1. SSID Employee (integrate with AD or other AAA)&lt;BR /&gt;2. SSID Guest (Voucher or Selfservice)&lt;BR /&gt;3. SSID Onboarding Portal&lt;BR /&gt;&lt;BR /&gt;With Zero-IT, client connect to the SSID Onboarding portal and choose "Register Device"(Employee) or &amp;nbsp;"Guest Access"(Guest) . The result is Client will automatically redirect to ssid Employee/Guest</description>
    <pubDate>Fri, 02 Jun 2017 07:02:39 GMT</pubDate>
    <dc:creator>irvan_irvan</dc:creator>
    <dc:date>2017-06-02T07:02:39Z</dc:date>
    <item>
      <title>why byod provisioning</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8128#M22</link>
      <description>Hi everyone,&lt;BR /&gt;&lt;BR /&gt;I have recently seen this video here:&amp;nbsp;&lt;A href="https://www.youtube.com/watch?v=9AUki6_lJPA" rel="nofollow" title="Link: https://www.youtube.com/watch?v=9AUki6_lJPA"&gt;https://www.youtube.com/watch?v=9AUki6_lJPA&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;So, in short - the guy makes 3 wlans and 3 roles so that each role can connect just to 1 wlan. And then he makes a provisioning hotspot where users authenticate using username and password,&amp;nbsp;and get automatically redirected to their wlan (zero-it activation). Can someone point out to me what are the benefits of this approach compared to not having a provisioning wlan, but instead users connect to their wlan and then autenthicate there using a username/password combination (802.1x using internal database on the controller).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;It seems to me that it's just one wlan more (the hotspot) for the same service, but surely I'm wrong.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 30 May 2017 08:35:49 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8128#M22</guid>
      <dc:creator>marko_markovic_</dc:creator>
      <dc:date>2017-05-30T08:35:49Z</dc:date>
    </item>
    <item>
      <title>Re: why byod provisioning</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8129#M23</link>
      <description>Hi Marko,&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp; Using 802.1x with userid/pw and assigned roles is great security, your AAA server&lt;BR /&gt;can pass back attributes to set lots of things from VLAN to permitted WLANs, etc.&amp;nbsp; &lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Zero-IT is often used for multiple device access permissions, like your phone and &lt;BR /&gt;laptop, onto a WPA2-PSK type WLAN and works well for Education and Hospitality &lt;BR /&gt;deployments.&amp;nbsp; One solution is to use a HotSpot WLAN to redirect clients to the Zero-IT&lt;BR /&gt;provisioning utility.</description>
      <pubDate>Wed, 31 May 2017 16:47:20 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8129#M23</guid>
      <dc:creator>michael_brado</dc:creator>
      <dc:date>2017-05-31T16:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: why byod provisioning</title>
      <link>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8130#M24</link>
      <description>This is the powerfull feature. For example you want create ssid for Employee(integrate with Active Directory) &amp;amp; Guest on 1 onboarding portal. The step is create:&lt;BR /&gt;1. SSID Employee (integrate with AD or other AAA)&lt;BR /&gt;2. SSID Guest (Voucher or Selfservice)&lt;BR /&gt;3. SSID Onboarding Portal&lt;BR /&gt;&lt;BR /&gt;With Zero-IT, client connect to the SSID Onboarding portal and choose "Register Device"(Employee) or &amp;nbsp;"Guest Access"(Guest) . The result is Client will automatically redirect to ssid Employee/Guest</description>
      <pubDate>Fri, 02 Jun 2017 07:02:39 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Cloudpath-Enrollment-System-ES/why-byod-provisioning/m-p/8130#M24</guid>
      <dc:creator>irvan_irvan</dc:creator>
      <dc:date>2017-06-02T07:02:39Z</dc:date>
    </item>
  </channel>
</rss>

