<?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: Hard Code Redirection URL with Captive Portal in ZoneDirector</title>
    <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15351#M3326</link>
    <description>Any advances on this feature yet ?</description>
    <pubDate>Wed, 31 May 2017 06:16:01 GMT</pubDate>
    <dc:creator>shaun_van_tond1</dc:creator>
    <dc:date>2017-05-31T06:16:01Z</dc:date>
    <item>
      <title>Hard Code Redirection URL with Captive Portal</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15347#M3322</link>
      <description>The feature exists within the guest wireless configuration to specify a url that you want users to be redirected to after successfully logging in.  I would find it quite useful to have the same functionality when authenticating users via AD/captive portal on a per wlan basis.
&lt;BR /&gt;&lt;BR /&gt;
Right now there is no method of changing the url users are sent to after being granted access, they just redirect to the website they had loaded.</description>
      <pubDate>Thu, 26 Jun 2014 21:08:26 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15347#M3322</guid>
      <dc:creator>damien_miller_1</dc:creator>
      <dc:date>2014-06-26T21:08:26Z</dc:date>
    </item>
    <item>
      <title>Re: Hard Code Redirection URL with Captive Portal</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15348#M3323</link>
      <description>voted up. Make sense to me.</description>
      <pubDate>Fri, 27 Jun 2014 10:37:06 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15348#M3323</guid>
      <dc:creator>monnat_systems</dc:creator>
      <dc:date>2014-06-27T10:37:06Z</dc:date>
    </item>
    <item>
      <title>Re: Hard Code Redirection URL with Captive Portal</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15349#M3324</link>
      <description>Yup... Would make the process of streamlining a device MDM push a whole lot easier too!</description>
      <pubDate>Fri, 27 Jun 2014 18:50:50 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15349#M3324</guid>
      <dc:creator>martin_kane</dc:creator>
      <dc:date>2014-06-27T18:50:50Z</dc:date>
    </item>
    <item>
      <title>Re: Hard Code Redirection URL with Captive Portal</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15350#M3325</link>
      <description>Any news?...</description>
      <pubDate>Tue, 08 Mar 2016 15:43:54 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15350#M3325</guid>
      <dc:creator>nicolas_fuentes</dc:creator>
      <dc:date>2016-03-08T15:43:54Z</dc:date>
    </item>
    <item>
      <title>Re: Hard Code Redirection URL with Captive Portal</title>
      <link>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15351#M3326</link>
      <description>Any advances on this feature yet ?</description>
      <pubDate>Wed, 31 May 2017 06:16:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/ZoneDirector/Hard-Code-Redirection-URL-with-Captive-Portal/m-p/15351#M3326</guid>
      <dc:creator>shaun_van_tond1</dc:creator>
      <dc:date>2017-05-31T06:16:01Z</dc:date>
    </item>
  </channel>
</rss>

