<?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 Cisco WLC guest WiFi - logout website in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/cisco-wlc-guest-wifi-logout-website/m-p/4405341#M229491</link>
    <description>&lt;P&gt;We are planning to use a Cisco 5508 wireless controller for guest WiFi.&lt;BR /&gt;Therefore I downloaded the example webauth_bundles from the Cisco download portal and customized it.&lt;BR /&gt;The Login process works fine with these files.&lt;BR /&gt;Here comes my first question:&lt;BR /&gt;If I am using a customized web authentication, the URL of the landing page is &lt;STRONG&gt;&lt;A href="https://192.0.2.1/fs/customwebauth/login.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/fs/customwebauth/login.html&lt;/A&gt;&lt;/STRONG&gt;&lt;BR /&gt;But if I browse to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/login.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/login.html&lt;/A&gt;&lt;/STRONG&gt;, the default Cisco web authentication (&lt;EM&gt;Internal (Default)&lt;/EM&gt;) appears.&lt;BR /&gt;Is it possible to place my customized bundle in the root directory so nobody can find the default Cisco page?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After successful login, I redirect to the logoff page where the user can press on the Logout button to log off.&lt;BR /&gt;The logout.html is the original from the webauth_bundles with our customizing settings.&lt;BR /&gt;The action in this original file (logout.html) redirects to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/logout.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/logout.html&lt;/A&gt;&lt;/STRONG&gt;.&lt;BR /&gt;Since I cannot customize this page, I would like to refer to my logout.html.&lt;BR /&gt;However, the result is different.&lt;BR /&gt;When referring from my site to my site, I get the HTTP error "405 - Method not allowed" (3b in my picture).&lt;BR /&gt;If I use the forwarding to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/logout.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/logout.html&lt;/A&gt;&lt;/STRONG&gt; (as it is set in the default) - means referring from my site to the logout.html in the root directory - I get to the webpage in the appendix (screenshot.png) (3a in my picture) and then log out works.&lt;BR /&gt;If my first question was answered positively, means that I can change the files in the root folder, I assume that this problem is unnecessary.&lt;BR /&gt;If I don't have the opportunity to overwrite the files in the root folder, I look for a solution to the 405 error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because I think my description of the problem is a little bit confusing, I tried to draw a little picture so the understanding would be easier (drawing.png).&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 20:19:14 GMT</pubDate>
    <dc:creator>Alex@IT</dc:creator>
    <dc:date>2021-07-05T20:19:14Z</dc:date>
    <item>
      <title>Cisco WLC guest WiFi - logout website</title>
      <link>https://community.cisco.com/t5/wireless/cisco-wlc-guest-wifi-logout-website/m-p/4405341#M229491</link>
      <description>&lt;P&gt;We are planning to use a Cisco 5508 wireless controller for guest WiFi.&lt;BR /&gt;Therefore I downloaded the example webauth_bundles from the Cisco download portal and customized it.&lt;BR /&gt;The Login process works fine with these files.&lt;BR /&gt;Here comes my first question:&lt;BR /&gt;If I am using a customized web authentication, the URL of the landing page is &lt;STRONG&gt;&lt;A href="https://192.0.2.1/fs/customwebauth/login.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/fs/customwebauth/login.html&lt;/A&gt;&lt;/STRONG&gt;&lt;BR /&gt;But if I browse to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/login.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/login.html&lt;/A&gt;&lt;/STRONG&gt;, the default Cisco web authentication (&lt;EM&gt;Internal (Default)&lt;/EM&gt;) appears.&lt;BR /&gt;Is it possible to place my customized bundle in the root directory so nobody can find the default Cisco page?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After successful login, I redirect to the logoff page where the user can press on the Logout button to log off.&lt;BR /&gt;The logout.html is the original from the webauth_bundles with our customizing settings.&lt;BR /&gt;The action in this original file (logout.html) redirects to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/logout.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/logout.html&lt;/A&gt;&lt;/STRONG&gt;.&lt;BR /&gt;Since I cannot customize this page, I would like to refer to my logout.html.&lt;BR /&gt;However, the result is different.&lt;BR /&gt;When referring from my site to my site, I get the HTTP error "405 - Method not allowed" (3b in my picture).&lt;BR /&gt;If I use the forwarding to &lt;STRONG&gt;&lt;A href="https://192.0.2.1/logout.html" target="_blank" rel="noopener"&gt;https://192.0.2.1/logout.html&lt;/A&gt;&lt;/STRONG&gt; (as it is set in the default) - means referring from my site to the logout.html in the root directory - I get to the webpage in the appendix (screenshot.png) (3a in my picture) and then log out works.&lt;BR /&gt;If my first question was answered positively, means that I can change the files in the root folder, I assume that this problem is unnecessary.&lt;BR /&gt;If I don't have the opportunity to overwrite the files in the root folder, I look for a solution to the 405 error.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Because I think my description of the problem is a little bit confusing, I tried to draw a little picture so the understanding would be easier (drawing.png).&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 20:19:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cisco-wlc-guest-wifi-logout-website/m-p/4405341#M229491</guid>
      <dc:creator>Alex@IT</dc:creator>
      <dc:date>2021-07-05T20:19:14Z</dc:date>
    </item>
  </channel>
</rss>

