<?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: guest authentication in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116190#M140329</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using WebAuth, the answer is no. The WLAN has a session timeout which is a hard timer and when this value expires the session is automatically terminated and the client has to login again. You can disable this feature, but then the idle timer is the next value that starts to count down when the device goes idle. You can adjust this, but I wouldn't adjust this value too high. 2-4 hours is what I use.&lt;BR /&gt;&lt;BR /&gt;So basically users will have to login everyday.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 31 Jan 2013 14:06:04 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2013-01-31T14:06:04Z</dc:date>
    <item>
      <title>guest authentication</title>
      <link>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116189#M140328</link>
      <description>&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; dear experts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;we are authenticating our wireless gests via controller web policy&lt;/P&gt;&lt;P&gt;but with this method, users must login every day however in corp-wireless we can define the profile with necessary security settings so the client will connect automatically&lt;/P&gt;&lt;P&gt;is it possible the controller will remember of guest clients&amp;nbsp; ?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 06:27:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116189#M140328</guid>
      <dc:creator>ohassairi</dc:creator>
      <dc:date>2021-07-04T06:27:16Z</dc:date>
    </item>
    <item>
      <title>Re: guest authentication</title>
      <link>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116190#M140329</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When using WebAuth, the answer is no. The WLAN has a session timeout which is a hard timer and when this value expires the session is automatically terminated and the client has to login again. You can disable this feature, but then the idle timer is the next value that starts to count down when the device goes idle. You can adjust this, but I wouldn't adjust this value too high. 2-4 hours is what I use.&lt;BR /&gt;&lt;BR /&gt;So basically users will have to login everyday.&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support iPhone App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2013 14:06:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116190#M140329</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-01-31T14:06:04Z</dc:date>
    </item>
    <item>
      <title>guest authentication</title>
      <link>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116191#M140330</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;"If" you really need to allow these "particular" guests more permanent access-or at least without the hassle of logging in, not that it's "that" intense- but a Mac Filter Bypass for WebAuth is an "option" (just throwing this out there).&amp;nbsp; I believe this was added in 7.0.116.0, however does not work properly for foreign/anchor scenarios until later releases&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not sure your current version, but this is from 7.2 config guide&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_wlan.html#wp1662912"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.2/configuration/guide/cg_wlan.html#wp1662912&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Again, this is an "option" you have, but you would need to make sure you add the desired guest/device MAC to your WLC's MAC Filter page and remove them when done.&lt;/P&gt;&lt;H3 style="font-size: 13px; color: #000000; font-family: Arial, Helvetica, sans-serif; margin: 14px 0em 7px -0.1in; background-color: #ffffff;"&gt;Information About Fallback Policy with MAC Filtering and Web Authentication&lt;/H3&gt;&lt;P&gt; &lt;A name="wp1460244" style="color: #000000; font-family: Arial, Helvetica, sans-serif; background-color: #ffffff;"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 12px; margin: 1px 0em 6px; background-color: #ffffff;"&gt;You can configure a fallback policy mechanism that combines Layer 2 and Layer 3 security. In a scenario where you have both MAC filtering and web authentication implemented, when a client tries to connect to a WLAN using the MAC filter (RADIUS server), if the client fails the authentication, you can configure the authentication to fall back to web authentication. When a client passes the MAC filter authentication, the web authentication is skipped and the client is connected to the WLAN. With this feature, you can avoid disassociations based on only a MAC filter authentication failure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 31 Jan 2013 21:16:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/guest-authentication/m-p/2116191#M140330</guid>
      <dc:creator>David Watkins</dc:creator>
      <dc:date>2013-01-31T21:16:27Z</dc:date>
    </item>
  </channel>
</rss>

