<?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: Client Timeout for WISPR in Access Points - Indoor and Outdoor</title>
    <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3239#M184</link>
    <description>We have an integration with Aruba Controller that allowsWiFI clients to login via our externally hosted splash page.The splash page makes the WiFi client's browser call"/auth/index.html/u" to our RADIUS server with certainprogrammatically generated credentials. &lt;BR /&gt;&lt;BR /&gt;see: &lt;A href="https://plex.software/" rel="nofollow"&gt;Plex&lt;/A&gt; &lt;A href="https://luckypatcher.pro/" rel="nofollow"&gt;Lucky Patcher&lt;/A&gt; &lt;A href="https://kodi.software/" rel="nofollow"&gt;Kodi&lt;/A&gt;</description>
    <pubDate>Wed, 23 May 2018 01:59:01 GMT</pubDate>
    <dc:creator>athman_abed</dc:creator>
    <dc:date>2018-05-23T01:59:01Z</dc:date>
    <item>
      <title>Client Timeout for WISPR</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3237#M182</link>
      <description>Does anyone think that the timeout for the wispr authentication on the smartzone 100 should be allowed to be longer than 10 days? I feel like we should be able to set it for at least a few months, but that's only my own personal opinion.</description>
      <pubDate>Wed, 06 Apr 2016 12:15:44 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3237#M182</guid>
      <dc:creator>justin_lawless</dc:creator>
      <dc:date>2016-04-06T12:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Client Timeout for WISPR</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3238#M183</link>
      <description>Hi Justin,&lt;BR /&gt;&lt;BR /&gt;I agree with your question but want to better understand the use case of your requirement. I request you to get in touch with your regional Ruckus System Engineer on this query.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ravi Teja</description>
      <pubDate>Fri, 11 May 2018 09:00:14 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3238#M183</guid>
      <dc:creator>ravi_teja_9zbkf</dc:creator>
      <dc:date>2018-05-11T09:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: Client Timeout for WISPR</title>
      <link>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3239#M184</link>
      <description>We have an integration with Aruba Controller that allowsWiFI clients to login via our externally hosted splash page.The splash page makes the WiFi client's browser call"/auth/index.html/u" to our RADIUS server with certainprogrammatically generated credentials. &lt;BR /&gt;&lt;BR /&gt;see: &lt;A href="https://plex.software/" rel="nofollow"&gt;Plex&lt;/A&gt; &lt;A href="https://luckypatcher.pro/" rel="nofollow"&gt;Lucky Patcher&lt;/A&gt; &lt;A href="https://kodi.software/" rel="nofollow"&gt;Kodi&lt;/A&gt;</description>
      <pubDate>Wed, 23 May 2018 01:59:01 GMT</pubDate>
      <guid>https://community.ruckuswireless.com/t5/Access-Points-Indoor-and-Outdoor/Client-Timeout-for-WISPR/m-p/3239#M184</guid>
      <dc:creator>athman_abed</dc:creator>
      <dc:date>2018-05-23T01:59:01Z</dc:date>
    </item>
  </channel>
</rss>

