<?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 Yes you can do this as well in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884565#M68804</link>
    <description>&lt;P&gt;Yes you can do this as well using a radius attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;1. The acl would live on the WLC. Sounds like you would have 2. One for peap and one for TLS.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;2. You create a policy in radius that says if users x comes in with TLS apply this name acl. That name matches the one in the WLC. When the radius success is returned to to the WLC that radius attribute with acl name is inside. So client goes into run state and the WLC apples that acl.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Make sense ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Since this his is radius backend stuff I don't think the 7.6 version is a problem.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Apr 2016 12:47:36 GMT</pubDate>
    <dc:creator>George Stefanick</dc:creator>
    <dc:date>2016-04-21T12:47:36Z</dc:date>
    <item>
      <title>Profile Wi-Fi users by authentication type</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884557#M68796</link>
      <description>&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;Is it possible to profile Wi-Fi users by authentication type (i.e. EAP-TLS, EAP-PEAP) with ability to segment via VLAN or through the use of ACL’s restricting access for non-corporate devices (BYOD) and corporate assets? For example, EAP-PEAP users (BYOD) would be restricted to just the Internet through an ACL or segmented VLAN while corporate assets using EAP-TLS would be allowed to Intranet resources in the same manner. Today, both non-corporate devices (BYOD) and corporate assets use the same SSID and the customer would like to keep the same SSID for both if possible. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;We are using Cisco Wireless LAN Controller (WLC) 2504 and 5508 running Release 7.6&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="color: #1f497d;"&gt;Gregg&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 11:55:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884557#M68796</guid>
      <dc:creator>GW M</dc:creator>
      <dc:date>2021-07-05T11:55:37Z</dc:date>
    </item>
    <item>
      <title>Yes you can do it but you</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884558#M68797</link>
      <description>&lt;P&gt;Yes you can do it but you will need a RADIUS server to create policies.&lt;/P&gt;
&lt;P&gt;How to do it:&lt;/P&gt;
&lt;P&gt;http://www.labminutes.com/sec0186_ise_13_wireless_dot1x_eap-tls_peap_1&lt;/P&gt;
&lt;P&gt;....and further videos on web.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Don't forget to rate helpful posts&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:11:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884558#M68797</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2016-04-21T12:11:43Z</dc:date>
    </item>
    <item>
      <title>We aren't using 802.1x. We</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884559#M68798</link>
      <description>&lt;P&gt;We aren't using 802.1x. We want to handle this thru the profile for the wireless user. Plus, I'm not paying money for a video but thanks anyway.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Greg&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:16:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884559#M68798</guid>
      <dc:creator>GW M</dc:creator>
      <dc:date>2016-04-21T12:16:20Z</dc:date>
    </item>
    <item>
      <title>You can also use the OU in</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884560#M68799</link>
      <description>&lt;P&gt;You can also use the OU in the cert to build policy's.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:23:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884560#M68799</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-04-21T12:23:38Z</dc:date>
    </item>
    <item>
      <title>802.1X is the frame work used</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884561#M68800</link>
      <description>&lt;P&gt;802.1X is the frame work used by peap and TLS. If you are using peap and TLS you are usin 802.1X.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:25:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884561#M68800</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-04-21T12:25:18Z</dc:date>
    </item>
    <item>
      <title>Correct.. we do. </title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884562#M68801</link>
      <description>&lt;P&gt;Correct.. we do.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:31:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884562#M68801</guid>
      <dc:creator>GW M</dc:creator>
      <dc:date>2016-04-21T12:31:20Z</dc:date>
    </item>
    <item>
      <title>Ok. </title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884563#M68802</link>
      <description>&lt;P&gt;Ok.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Vlan moving for example is handle by using radius attributes. You build authentication and authorization policies to make this happen. Example if user x uses cert then move them to vlan 5. If user x users peap move them to vlan 10.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;This is magic happens on the radius server ..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:35:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884563#M68802</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-04-21T12:35:14Z</dc:date>
    </item>
    <item>
      <title>Can we leverage an ACL per</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884564#M68803</link>
      <description>&lt;P&gt;Can we leverage an ACL per authentication type, given that we don't have VLAN trunking implemented and all users go thru the same VLAN? Also, are you aware of any issues being able to implement this using&amp;nbsp;&lt;SPAN&gt;Cisco Wireless LAN Controller (WLC) 2504 and 5508 running Release 7.6?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Thanks&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Gregg&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:41:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884564#M68803</guid>
      <dc:creator>GW M</dc:creator>
      <dc:date>2016-04-21T12:41:26Z</dc:date>
    </item>
    <item>
      <title>Yes you can do this as well</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884565#M68804</link>
      <description>&lt;P&gt;Yes you can do this as well using a radius attribute.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;1. The acl would live on the WLC. Sounds like you would have 2. One for peap and one for TLS.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;2. You create a policy in radius that says if users x comes in with TLS apply this name acl. That name matches the one in the WLC. When the radius success is returned to to the WLC that radius attribute with acl name is inside. So client goes into run state and the WLC apples that acl.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Make sense ?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Since this his is radius backend stuff I don't think the 7.6 version is a problem.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:47:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884565#M68804</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-04-21T12:47:36Z</dc:date>
    </item>
    <item>
      <title>Make sense. I will give it a</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884566#M68805</link>
      <description>&lt;P&gt;Make sense.&amp;nbsp;&lt;SPAN&gt;I will give it a try&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Thank you&lt;/P&gt;
&lt;P&gt;Gregg&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:49:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884566#M68805</guid>
      <dc:creator>GW M</dc:creator>
      <dc:date>2016-04-21T12:49:49Z</dc:date>
    </item>
    <item>
      <title>Thank you for the rating ..</title>
      <link>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884567#M68806</link>
      <description>&lt;P&gt;Thank you for the rating .. Check back if you have problems ..&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Apr 2016 12:52:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/profile-wi-fi-users-by-authentication-type/m-p/2884567#M68806</guid>
      <dc:creator>George Stefanick</dc:creator>
      <dc:date>2016-04-21T12:52:43Z</dc:date>
    </item>
  </channel>
</rss>

