<?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 Vendor specific codes from Windows NPS in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Vendor-specific-codes-from-Windows-NPS/m-p/43322#M2391</link>
    <description>Hello what exactly is the 'Vendor specific' attribute that you define within Windows NPS for 802.1x RADIUS authentications.&lt;BR /&gt;This 'Vendor specific' attribute gets returned to the ZoneDirector after it makes an 802.1x authentication request. Does it have to be the exact name of the ESSID &amp;nbsp;that you are authenticating for /</description>
    <pubDate>Wed, 07 Mar 2018 20:00:47 GMT</pubDate>
    <dc:creator>philip_francis1</dc:creator>
    <dc:date>2018-03-07T20:00:47Z</dc:date>
    <item>
      <title>Vendor specific codes from Windows NPS</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Vendor-specific-codes-from-Windows-NPS/m-p/43322#M2391</link>
      <description>Hello what exactly is the 'Vendor specific' attribute that you define within Windows NPS for 802.1x RADIUS authentications.&lt;BR /&gt;This 'Vendor specific' attribute gets returned to the ZoneDirector after it makes an 802.1x authentication request. Does it have to be the exact name of the ESSID &amp;nbsp;that you are authenticating for /</description>
      <pubDate>Wed, 07 Mar 2018 20:00:47 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Vendor-specific-codes-from-Windows-NPS/m-p/43322#M2391</guid>
      <dc:creator>philip_francis1</dc:creator>
      <dc:date>2018-03-07T20:00:47Z</dc:date>
    </item>
  </channel>
</rss>

