<?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 Authentication failure to AD from vSZ 3.4 in To Be Moved</title>
    <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Authentication-failure-to-AD-from-vSZ-3-4/m-p/43400#M2392</link>
    <description>It appears that authentication to AD from vSZ 3.4 works to the AD ( CNCommon Name) rather than the SamAccountName  which it should do. Is there any way around this?</description>
    <pubDate>Mon, 10 Sep 2018 11:08:57 GMT</pubDate>
    <dc:creator>paddy_naughton_</dc:creator>
    <dc:date>2018-09-10T11:08:57Z</dc:date>
    <item>
      <title>Authentication failure to AD from vSZ 3.4</title>
      <link>https://community.ruckuswireless.com/t5/To-Be-Moved/Authentication-failure-to-AD-from-vSZ-3-4/m-p/43400#M2392</link>
      <description>It appears that authentication to AD from vSZ 3.4 works to the AD ( CNCommon Name) rather than the SamAccountName  which it should do. Is there any way around this?</description>
      <pubDate>Mon, 10 Sep 2018 11:08:57 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/To-Be-Moved/Authentication-failure-to-AD-from-vSZ-3-4/m-p/43400#M2392</guid>
      <dc:creator>paddy_naughton_</dc:creator>
      <dc:date>2018-09-10T11:08:57Z</dc:date>
    </item>
  </channel>
</rss>

