<?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: CWP - User Selection in Aerohive Migrated Content</title>
    <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/cwp-user-selection/m-p/66449#M3117</link>
    <description>&lt;P&gt;Hello Barry, thanks for the detailed explanation. Our CWPs don't have a split registration option per say, but we can direct clients to an external page for authentication if you have one set up with this capability. Or if it is known who is a tenant ahead of time, we could set up client classification to move tenants and guests to different user profiles within the same SSID, allowing us to give them different firewall policies, VLANs, QoS Settings, schedules, etc. Here is a guide for client classification in HiveManager, in case you're interested: &lt;A href="https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager" alt="https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager" target="_blank"&gt;https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 15 Apr 2019 17:33:21 GMT</pubDate>
    <dc:creator>samantha_lynn</dc:creator>
    <dc:date>2019-04-15T17:33:21Z</dc:date>
    <item>
      <title>CWP - User Selection</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/cwp-user-selection/m-p/66448#M3116</link>
      <description>&lt;P&gt;I am fairly new to Aerohive so please forgive if this is a simple question.&lt;/P&gt;&lt;P&gt;I have a use case where a customer would like to use CWP. This is fine, however upon connecting to a single SSID site wide, the customer would then like to give the end user 2 options; 'Are you a tenant' or 'are you a guest'. Is that possible? The idea would be to then present a self registration page for each option and authenticate using PPSK, the difference being that each option above would be associated with different user roles and in turn different vlans and traffic shaping/bandwidth allowances.&lt;/P&gt;&lt;P&gt;?&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2019 14:50:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/cwp-user-selection/m-p/66448#M3116</guid>
      <dc:creator>barrymcnicholl</dc:creator>
      <dc:date>2019-04-15T14:50:51Z</dc:date>
    </item>
    <item>
      <title>Re: CWP - User Selection</title>
      <link>https://community.extremenetworks.com/t5/aerohive-migrated-content/cwp-user-selection/m-p/66449#M3117</link>
      <description>&lt;P&gt;Hello Barry, thanks for the detailed explanation. Our CWPs don't have a split registration option per say, but we can direct clients to an external page for authentication if you have one set up with this capability. Or if it is known who is a tenant ahead of time, we could set up client classification to move tenants and guests to different user profiles within the same SSID, allowing us to give them different firewall policies, VLANs, QoS Settings, schedules, etc. Here is a guide for client classification in HiveManager, in case you're interested: &lt;A href="https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager" alt="https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager" target="_blank"&gt;https://thehivecommunity.aerohive.com/s/article/Client-Classification-in-HiveManager&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Apr 2019 17:33:21 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/aerohive-migrated-content/cwp-user-selection/m-p/66449#M3117</guid>
      <dc:creator>samantha_lynn</dc:creator>
      <dc:date>2019-04-15T17:33:21Z</dc:date>
    </item>
  </channel>
</rss>

