<?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: How Make the Web Auth Certificate Warning Go Away in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404488#M171803</link>
    <description>Correct... installing a trusted cert is the preferred way. Make sure that you can setup a DNS entry for the VIP in order for this to work. &lt;BR /&gt;</description>
    <pubDate>Sun, 24 Jun 2018 12:47:07 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2018-06-24T12:47:07Z</dc:date>
    <item>
      <title>How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404457#M171800</link>
      <description>&lt;P&gt;The issue is with wireless controller Mobility Express version 8.2.166 which is configured for guest WLAN.&lt;/P&gt;
&lt;P&gt;the issue happen user need to access to cisco page of local web authentication page the browser is not trusting the certificate from the virtual IP of WLAN controller.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;How to make the guest users access to web authentication&amp;nbsp; page directly without the SSL connection.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 15:46:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404457#M171800</guid>
      <dc:creator>Abdulkader Naji</dc:creator>
      <dc:date>2021-07-05T15:46:50Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404485#M171801</link>
      <description>You need to disable https in order to have guest portal use http. However, I believe this will also disable https/ssh for management. &lt;BR /&gt;</description>
      <pubDate>Sun, 24 Jun 2018 12:38:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404485#M171801</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2018-06-24T12:38:07Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404486#M171802</link>
      <description>&lt;P&gt;&lt;U&gt;I just open TAC case I got this below reply&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;U&gt;Problem Description:&lt;/U&gt;&lt;/P&gt;
&lt;P&gt;WLC: 2800s ME&lt;/P&gt;
&lt;P&gt;SW: 8.2.166.0&lt;/P&gt;
&lt;P&gt;You would like to avoid the security warning shown when using gust network.&lt;/P&gt;
&lt;P&gt;When using the CLI of the ME, you can use the same commands used on the normal WLC, so you can simply follow the link below, which provides a step by step procedure to do that:&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#anc7" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#anc7&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; &lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#anc14" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/109597-csr-chained-certificates-wlc-00.html#anc14&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I will try and revert back if it will work in my scenario&lt;/P&gt;</description>
      <pubDate>Sun, 24 Jun 2018 12:43:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404486#M171802</guid>
      <dc:creator>Abdulkader Naji</dc:creator>
      <dc:date>2018-06-24T12:43:26Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404488#M171803</link>
      <description>Correct... installing a trusted cert is the preferred way. Make sure that you can setup a DNS entry for the VIP in order for this to work. &lt;BR /&gt;</description>
      <pubDate>Sun, 24 Jun 2018 12:47:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404488#M171803</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2018-06-24T12:47:07Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404490#M171804</link>
      <description>&lt;P&gt;as TAC&amp;nbsp;suggested&lt;/P&gt;
&lt;P&gt;The easiest one is to use HTTP redirect instead of HTTPs, but our suggestion to use a certificate was to get rid of that error without the need to manually choose HTTP.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Jun 2018 13:06:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/3404490#M171804</guid>
      <dc:creator>Abdulkader Naji</dc:creator>
      <dc:date>2018-06-24T13:06:16Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4013337#M171805</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;Please can you advise me in same,&lt;/P&gt;&lt;P&gt;I believe we can use restart command on WLC 5520 to activate Web-authentication cert installed on WLC.&lt;/P&gt;&lt;P&gt;I am having two 5520 WLC in HA cluster, By giving command "Restart on self", will there be any down time for users connected to WiFi?&lt;/P&gt;&lt;P&gt;OR&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there any other way to&amp;nbsp;&lt;SPAN&gt;activate Web-authentication cert installed on WLC without down time&amp;nbsp;for users connected to WiFi?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 11:18:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4013337#M171805</guid>
      <dc:creator>Prkalavadia</dc:creator>
      <dc:date>2020-01-17T11:18:33Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4013394#M171806</link>
      <description>If you have SSO enabled, you can make your change on the primary, save the config and then issue a force failover. This way the active will restart and the secondary will become active. You can then configure the new active, save that config and wait until both units are up and synced before you issue another force failover. There will be no downtime as long as you restart one at a time. The primary is first because certificates are not synced in SSO. &lt;BR /&gt;</description>
      <pubDate>Fri, 17 Jan 2020 12:21:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4013394#M171806</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2020-01-17T12:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4029661#M171807</link>
      <description>Hi Scott,&lt;BR /&gt;As per your advise, I restarted Primary which failed over to secondary and after sometime I restarted Secondary so Again Primary became Active.&lt;BR /&gt;During this time I continues pinged to VIP, Zero packet drop , No down time,&lt;BR /&gt;And Uploaded WebAuth Certificate is active now.&lt;BR /&gt;Many thanks for your advise.&lt;BR /&gt;Punit</description>
      <pubDate>Fri, 14 Feb 2020 08:38:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4029661#M171807</guid>
      <dc:creator>Prkalavadia</dc:creator>
      <dc:date>2020-02-14T08:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4029721#M171808</link>
      <description>Glad that worked for you!&lt;BR /&gt;</description>
      <pubDate>Fri, 14 Feb 2020 10:18:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4029721#M171808</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2020-02-14T10:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: How Make the Web Auth Certificate Warning Go Away</title>
      <link>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4720282#M248178</link>
      <description>&lt;P&gt;Why it is necessary to setup a DNS entry? Would it work without this?&lt;/P&gt;</description>
      <pubDate>Sat, 12 Nov 2022 21:34:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/how-make-the-web-auth-certificate-warning-go-away/m-p/4720282#M248178</guid>
      <dc:creator>iores</dc:creator>
      <dc:date>2022-11-12T21:34:05Z</dc:date>
    </item>
  </channel>
</rss>

