<?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: ISE 2.4 and 9800 WLC: Wireless guest issue in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451307#M232446</link>
    <description>&lt;P&gt;Just remove the below lines as I mentioned before:&lt;BR /&gt;&lt;STRONG&gt;redirect on-success &amp;nbsp;&lt;A href="https://www.grammer.com/" target="_blank"&gt;https://www.grammer.com/&lt;/A&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;redirect portal ipv4 192.0.2.1&lt;/STRONG&gt;&lt;BR /&gt;with the above, this will be sent to ISE as Login, meaning to match on ISE you need Radius:Service-Type = Login&lt;BR /&gt;this is used if you have a Web server that provide you a portal or if you want to use one of the ISE portals, usually a copy of the sponsored Guest Portal, so in your case because you want to use the 9800 customized portal then you have to leave those fields empty by removing the above cli lines and that's mean when you check the username/pass with ISE (using ISE locally defined users or from Active Directory) then the 9800 will send those as "Outbound", Radius:Service-Type = Outbound&lt;BR /&gt;One more thing, in your ISE Policy Set, you're not telling ISE where to look and check for the usernames/pass that Guests will be using, meaning, if you need to check against AD group then you specify that group, if you need to check them against ISE local group you need to specify that. In below screenshot you can see that I'm using simple policy set to check both AD and internal ISE group without checking the service type, but you can definitely use that check too.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ISE Policy Set.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/128250iC6D4327B66AC8D0C/image-size/large?v=v2&amp;amp;px=999" role="button" title="ISE Policy Set.jpg" alt="ISE Policy Set.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 18 Aug 2021 16:00:23 GMT</pubDate>
    <dc:creator>Grendizer</dc:creator>
    <dc:date>2021-08-18T16:00:23Z</dc:date>
    <item>
      <title>ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448264#M232192</link>
      <description>&lt;P&gt;Hello Experts,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am facing a issue with guest access authentication. Old AIROS wlcs are working but now I have a installed a new 9800 wlc and its creating an issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Requesting help to troubleshoot below authentication fail error messages seen for wireless guest users.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Event&lt;/TD&gt;&lt;TD&gt;5400 Authentication failed&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Failure Reason&lt;/TD&gt;&lt;TD&gt;15039 Rejected per authorization profile&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Resolution&lt;/TD&gt;&lt;TD&gt;Authorization Profile with ACCESS_REJECT attribute was selected as a result of the matching authorization rule. Check the appropriate Authorization policy rule-results.&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Root cause&lt;/TD&gt;&lt;TD&gt;Selected Authorization Profile contains ACCESS_REJECT attribute&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Username&lt;/TD&gt;&lt;TD&gt;&lt;STRONG&gt;USERNAME&lt;/STRONG&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Its not hitting the right Authentication policy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Auth policies:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="AuthZ.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/127548i0C8AE055B9B4C6B1/image-size/large?v=v2&amp;amp;px=999" role="button" title="AuthZ.png" alt="AuthZ.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="authentication.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/127545i63116C753983EA20/image-size/large?v=v2&amp;amp;px=999" role="button" title="authentication.png" alt="authentication.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="1.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/127544i5B593D78ABC4357D/image-size/large?v=v2&amp;amp;px=999" role="button" title="1.png" alt="1.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;&lt;SPAN&gt;Steps&lt;/SPAN&gt;&lt;/H3&gt;&lt;TABLE border="0" cellpadding="3"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;11001&lt;/TD&gt;&lt;TD&gt;Received RADIUS Access-Request&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;11017&lt;/TD&gt;&lt;TD&gt;RADIUS created a new session&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15049&lt;/TD&gt;&lt;TD&gt;Evaluating Policy Group&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15008&lt;/TD&gt;&lt;TD&gt;Evaluating Service Selection Policy&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15048&lt;/TD&gt;&lt;TD&gt;Queried PIP&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15041&lt;/TD&gt;&lt;TD&gt;Evaluating Identity Policy&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15013&lt;/TD&gt;&lt;TD&gt;Selected Identity Source -&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;22043&lt;/TD&gt;&lt;TD&gt;&lt;FONT color="#FF0000"&gt;&lt;STRONG&gt;Current Identity Store does not support the authentication method; Skipping it&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;22064&lt;/TD&gt;&lt;TD&gt;Authentication method is not supported by any applicable identity store(s)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;22058&lt;/TD&gt;&lt;TD&gt;The advanced option that is configured for an unknown user is used&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;22060&lt;/TD&gt;&lt;TD&gt;The 'Continue' advanced option is configured in case of a failed authentication request&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;24715&lt;/TD&gt;&lt;TD&gt;ISE has not confirmed locally previous successful machine authentication for user in Active Directory&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15036&lt;/TD&gt;&lt;TD&gt;Evaluating Authorization Policy&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15048&lt;/TD&gt;&lt;TD&gt;Queried PIP&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15048&lt;/TD&gt;&lt;TD&gt;Queried PIP&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15048&lt;/TD&gt;&lt;TD&gt;Queried PIP&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15016&lt;/TD&gt;&lt;TD&gt;Selected Authorization Profile - DenyAccess&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;15039&lt;/TD&gt;&lt;TD&gt;Rejected per authorization profile&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;11003&lt;/TD&gt;&lt;TD&gt;Returned RADIUS Access-Reject&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;&lt;TD&gt;5434&lt;/TD&gt;&lt;TD&gt;Endpoint conducted several failed authentications of the same scenario&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Sep 2021 09:47:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448264#M232192</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-09-21T09:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448718#M232235</link>
      <description>&lt;P&gt;&lt;STRONG&gt;15039 Rejected per authorization profile&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you show the full failure log, please?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Aug 2021 22:29:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448718#M232235</guid>
      <dc:creator>craig.beck</dc:creator>
      <dc:date>2021-08-12T22:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448858#M232245</link>
      <description>&lt;P&gt;which logs you want to me paste&amp;nbsp; ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;from ISE side or debug from WLC ?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 07:50:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4448858#M232245</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-08-13T07:50:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450071#M232347</link>
      <description>&lt;P&gt;you need to change (redirect portal ipv4 192.0.2.1) to the ISE IP Address instead.&lt;/P&gt;
&lt;P&gt;Check this line (redirect for-login guest.corp.com) Which ISE portal will reply the requests?&lt;/P&gt;
&lt;P&gt;you're using Guest Users (meaning the users are configured in ISE)&lt;/P&gt;
&lt;P&gt;not sure about this condition: WLC_Web_Authentication (it needs to check ISE Guest Users group as you specified in AuthC rule)&lt;/P&gt;
&lt;P&gt;moreover, ISE portal is using by default TCP port 8443 and with that you will need to create a Pre-Auth ACL that will be applied on the WLAN &amp;gt; Security &amp;gt; Layer3 &amp;gt; Preauthentication ACL &amp;gt; IPv4, example ACL below:&lt;/P&gt;
&lt;P&gt;permit tcp any host ISE_IP_ADDRESS eq 8443&lt;/P&gt;
&lt;P&gt;permit tcp host ISE_IP_ADDRESS eq 8443 any&lt;/P&gt;
&lt;P&gt;permit tcp any any eq domain&lt;/P&gt;
&lt;P&gt;permit udp any any eq domain&lt;/P&gt;
&lt;P&gt;permit udp any any eq bootpc&lt;/P&gt;
&lt;P&gt;permit udp any any eq bootps&lt;/P&gt;
&lt;P&gt;deny ip any any&lt;/P&gt;</description>
      <pubDate>Mon, 16 Aug 2021 17:47:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450071#M232347</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2021-08-16T17:47:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450257#M232360</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your input but I am using Portal on customized WLC itself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Portal is on WLC&lt;/P&gt;&lt;P&gt;Guest users are in ISE sponsor Portal&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Tue, 17 Aug 2021 05:10:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450257#M232360</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-08-17T05:10:25Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450636#M232389</link>
      <description>&lt;P&gt;Ok, then you need to do these changes:&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;Changes on 9800:&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;Add the below command:&lt;BR /&gt;&lt;STRONG&gt;aaa authentication webauth default local group ISE&lt;/STRONG&gt;&lt;BR /&gt;to check the WLC local users first then ISE, if you need to check the 9800 local users/guest accounts then you have to add this line too (&lt;STRONG&gt;aaa authorization network default local&lt;/STRONG&gt;)&lt;BR /&gt;OR&lt;BR /&gt;&lt;STRONG&gt;aaa authentication webauth default group ISE&lt;/STRONG&gt;&lt;BR /&gt;to check the users from ISE only&lt;BR /&gt;Note: "Named Method lists not supported for webauth" so in your case we can't use the method list ISE so instead we have to use default as in above cli.&lt;BR /&gt;also you shouldn't use the below lines under global parameter map: (by the way you can use different "new" parameter map and will work too, meaning doesn't have to be the global parameter map but that works too)&lt;BR /&gt;&lt;STRONG&gt;redirect for-login guest.corp.com&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;redirect portal ipv4 192.0.2.1&lt;/STRONG&gt;&lt;BR /&gt;Because if you want to use guest.corp.com as the DNS name to the ipv4 virtual IP address then you need to put that in (Virtual IPv4 Hostname) section also you need a DNS record to point the guests to the 9800 virtual IP address, meaning, DNS record for guest.corp.com=192.0.2.1 and of course you need a certificate signed by public CA (with SAN) so guests will not see certificate error, info is here &lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213917-generate-csr-for-third-party-certificate.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213917-generate-csr-for-third-party-certificate.html&lt;/A&gt;&lt;BR /&gt;side note: i didn't see ISE1 as RADIUS configured but it used under group ISE so either you configure that or remove it from that group&lt;BR /&gt;for more info, check this doc Custom Web Authentication on Catalyst 9800 Wireless Controllers Configuration Example&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/216121-custom-web-authentication-on-catalyst-98.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/216121-custom-web-authentication-on-catalyst-98.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;&lt;STRONG&gt;Changes on ISE:&lt;/STRONG&gt;&lt;/U&gt;&lt;BR /&gt;You're using (WLC_Web_Authentication) as a condition, the rules for this condition are:&lt;BR /&gt;Radius:NAS-Port-Type = Wireless - IEEE 802.11&lt;BR /&gt;Radius:Service-Type = Login&lt;BR /&gt;while in this case the Service Type is "Outbound" so will not match your rule, so you need to remove that condition or create a new one with Radius:Service-Type = Outbound&lt;/P&gt;</description>
      <pubDate>Tue, 17 Aug 2021 17:02:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4450636#M232389</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2021-08-17T17:02:09Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451017#M232419</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/370003"&gt;@Grendizer&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for detailed explanation!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I did as you mentioned above but still hitting the default policy with Deny Access:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. Method list name created with name "default"&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;aaa authentication login default local group ISE&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;aaa authentication webauth default local group ISE&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. New Parameter MAP:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;parameter-map type webauth LWA&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;type webauth&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;sleeping-client&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;redirect portal ipv4 192.0.2.1&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;logout-window-disabled&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;success-window-disable&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;cisco-logo-disable&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3. Changes on ISE:&lt;/P&gt;&lt;P&gt;Authentication&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="9800_Web1.PNG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/128210i4B57FEFE1935E0A8/image-size/large?v=v2&amp;amp;px=999" role="button" title="9800_Web1.PNG" alt="9800_Web1.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="9800_Web.PNG" style="width: 647px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/128209i68D4BD64192896B1/image-size/large?v=v2&amp;amp;px=999" role="button" title="9800_Web.PNG" alt="9800_Web.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;AuthZ&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="9800_Web_Authz.PNG" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/128211iA79F3263D6FAB52C/image-size/large?v=v2&amp;amp;px=999" role="button" title="9800_Web_Authz.PNG" alt="9800_Web_Authz.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;SSId Config:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;wlan CorpGuest 1 CorpGuest&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;peer-blocking drop&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;no security wpa&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;no security wpa wpa2&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;no security wpa wpa2 ciphers aes&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;no security wpa akm dot1x&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;security web-auth&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;security web-auth authentication-list default&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;security web-auth parameter-map LWA&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" color="#008000"&gt;no shutdown&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Bets Regards&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Sep 2021 09:49:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451017#M232419</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-09-21T09:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451307#M232446</link>
      <description>&lt;P&gt;Just remove the below lines as I mentioned before:&lt;BR /&gt;&lt;STRONG&gt;redirect on-success &amp;nbsp;&lt;A href="https://www.grammer.com/" target="_blank"&gt;https://www.grammer.com/&lt;/A&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;redirect portal ipv4 192.0.2.1&lt;/STRONG&gt;&lt;BR /&gt;with the above, this will be sent to ISE as Login, meaning to match on ISE you need Radius:Service-Type = Login&lt;BR /&gt;this is used if you have a Web server that provide you a portal or if you want to use one of the ISE portals, usually a copy of the sponsored Guest Portal, so in your case because you want to use the 9800 customized portal then you have to leave those fields empty by removing the above cli lines and that's mean when you check the username/pass with ISE (using ISE locally defined users or from Active Directory) then the 9800 will send those as "Outbound", Radius:Service-Type = Outbound&lt;BR /&gt;One more thing, in your ISE Policy Set, you're not telling ISE where to look and check for the usernames/pass that Guests will be using, meaning, if you need to check against AD group then you specify that group, if you need to check them against ISE local group you need to specify that. In below screenshot you can see that I'm using simple policy set to check both AD and internal ISE group without checking the service type, but you can definitely use that check too.&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ISE Policy Set.jpg" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/128250iC6D4327B66AC8D0C/image-size/large?v=v2&amp;amp;px=999" role="button" title="ISE Policy Set.jpg" alt="ISE Policy Set.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Aug 2021 16:00:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451307#M232446</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2021-08-18T16:00:23Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451601#M232468</link>
      <description>&lt;P&gt;Thanks, I will configure the policies as you mentioned and will give a try and let you know!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Best Regards&lt;/P&gt;</description>
      <pubDate>Thu, 19 Aug 2021 05:06:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4451601#M232468</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-08-19T05:06:49Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4464694#M233254</link>
      <description>&lt;P&gt;Thank you. It working now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could you please also tell me how to install a wildcard certificate for webauth certificate eon 9800 WLC?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Sep 2021 07:22:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4464694#M233254</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-09-13T07:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4464772#M233259</link>
      <description>&lt;P&gt;Check this link:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://thewlan.com.au/2020/07/14/9800-local-webauth-certs/" target="_blank"&gt;https://thewlan.com.au/2020/07/14/9800-local-webauth-certs/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to rate helpful posts&lt;/P&gt;</description>
      <pubDate>Mon, 13 Sep 2021 08:45:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4464772#M233259</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2021-09-13T08:45:27Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4465124#M233279</link>
      <description>Check this doc:&lt;BR /&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213917-generate-csr-for-third-party-certificate.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213917-generate-csr-for-third-party-certificate.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Sep 2021 14:59:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4465124#M233279</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2021-09-13T14:59:06Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4466004#M233319</link>
      <description>&lt;P&gt;I will try to install it and let you know.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 14 Sep 2021 11:29:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4466004#M233319</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-09-14T11:29:09Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4470540#M233513</link>
      <description>&lt;P&gt;You can try this method as well.. I tried in my lab and it worked:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;First you need to create a trustpoint on the WLC. The trustpoint contains the certificate authority that signed the certificate in use.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#008000"&gt;&lt;EM&gt;WLC1&lt;/EM&gt;&lt;EM&gt; (config)#crypto pki trustpoint WILDCARD&lt;/EM&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;EM&gt;WLC1 (ca-trustpoint)#fqdn *.xyz.com&lt;/EM&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;EM&gt;WLC1 (ca-trustpoint)#subject-name cn=*.xyz.com&lt;/EM&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;EM&gt;WLC1 (ca-trustpoint)#revocation-check crl&lt;/EM&gt;&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;EM&gt;WLC1 (ca-trustpoint)#rsakeypair WILDCARD&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;Next, you should import the certificate. There are multiple ways for importing the certificate, but you can use FTP/tftp to transfer the certificate from your laptop to the wlc.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Info: Certificate must be in PKCS12 (.pfx) form&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;WLC1(config)#&lt;FONT color="#008000"&gt;crypto pki import WILDCARD pkcs12 ftp: password xyz12345&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;% Importing pkcs12...&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Address or name of remote host []? &lt;FONT color="#008000"&gt;192.168.21.25&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Source filename [WILDCARD]? &lt;FONT color="#008000"&gt;WildcardCert.pfx&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Reading file from &lt;A href="ftp://192.168.21.25/WildcardCert.pfx" target="_blank"&gt;ftp://192.168.21.25/WildcardCert.pfx&lt;/A&gt;!&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;[OK - 6048/4096 bytes]&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;% The CA cert is not self-signed.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;% Do you also want to create trustpoints for CAs higher in&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;% the hierarchy? [yes/no]:&lt;FONT color="#008000"&gt;yes&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;*Sep 16 10:38:02 UTC: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named WILDCARD has been generated or imported by pki-pkcs12&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;CRYPTO_PKI: Imported PKCS12 file successfully.&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#008000"&gt;&lt;EM&gt;WLC1(config)#exit&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;FONT size="2" color="#008000"&gt;&lt;EM&gt;WLC1(config)#wr&lt;/EM&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;*Sep 16 10:38:06 UTC: %PKI-6-TRUSTPOINT_CREATE: Trustpoint: WILDCARD-rrr1 created succesfully&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;*Sep 16 10:38:06 UTC: %PKI-6-PKCS12_IMPORT_SUCCESS: PKCS #12 import in to trustpoint WILDCARD successfully imported. &lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;The certificate is now successfully imported into the WLC and can be associated with the Webauth wlan.&lt;/P&gt;
&lt;P&gt;then you can assign wildcard certificate to webauth parameter map.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;P&gt;Dont forget to arte helpful posts&lt;/P&gt;</description>
      <pubDate>Tue, 21 Sep 2021 08:30:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4470540#M233513</guid>
      <dc:creator>Sandeep Choudhary</dc:creator>
      <dc:date>2021-09-21T08:30:57Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4470542#M233514</link>
      <description>&lt;P&gt;Thank you I will try it!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Could &lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/370003"&gt;@Grendizer&lt;/a&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/323059"&gt;@Sandeep Choudhary&lt;/a&gt;&amp;nbsp;please help me about this issue ? Here is the post about my Mobility express issue:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cisco.com/t5/wireless/mobility-express-issue-with-ise-amp-cloud-radius-server/m-p/4466968#M233371" target="_blank"&gt;https://community.cisco.com/t5/wireless/mobility-express-issue-with-ise-amp-cloud-radius-server/m-p/4466968#M233371&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;</description>
      <pubDate>Tue, 21 Sep 2021 08:34:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4470542#M233514</guid>
      <dc:creator>ittechk4u1</dc:creator>
      <dc:date>2021-09-21T08:34:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679749#M245623</link>
      <description>&lt;P&gt;Hi Grendizer,&lt;/P&gt;&lt;P&gt;I have a third-party certificate installed but when I put the guest.corp.com name for the certificate the guests get a "This site can't be reached" when it redirects to the name I put in.&amp;nbsp; I believe this is because I need to enter a DNS record for guest.corp.com to 192.0.2.1 as you mentioned.&amp;nbsp; How do I go about doing that? Is it through Administration &amp;gt; DNS and then add DNS Server or is there a different page to add that DNS record?&amp;nbsp; Thanks for the hlep.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 13:16:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679749#M245623</guid>
      <dc:creator>meditinst</dc:creator>
      <dc:date>2022-09-01T13:16:16Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679822#M245628</link>
      <description>&lt;P&gt;Configuration &amp;gt; Security &amp;gt; Web Auth &amp;gt; global &amp;gt; General &amp;gt; &lt;BR /&gt;Virtual IPv4 Address: 192.0.2.1&lt;BR /&gt;Virtual IPv4 Hostname: guest.corp.com&lt;BR /&gt;and select the "Trustpoint" that contain your 3rd party cert &lt;BR /&gt;next, (from the DNS Server), you need to add to the DNS record to point the guests to the 9800 virtual IP address.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 15:10:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679822#M245628</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2022-09-01T15:10:51Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679834#M245630</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;It's that last part that I am confused about, what DNS server?&amp;nbsp; We are using our ISP's DNS servers for the guest wireless so will I have to change that to use our local DNS then?&amp;nbsp; If we use our local DNS is there a way for us to access the controller securely on the management IP vs guests accessing the virtual IP/DNS name when they sign in?&lt;/P&gt;&lt;P&gt;I am looking through the DHCP options, is it possible to add the ip and hostname there so we can keep the external DNS?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2022 15:28:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679834#M245630</guid>
      <dc:creator>meditinst</dc:creator>
      <dc:date>2022-09-01T15:28:12Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 and 9800 WLC: Wireless guest issue</title>
      <link>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679856#M245635</link>
      <description>The DNS query will be sent from the guests to the DNS to resolve guest.corp.com to 192.0.2.1 so no involvement from the WLC.&lt;BR /&gt;You can keep the external DNS for the guests but you can advertise the 192.0.2.1 IP Addresses to the public DNS as "forward only" DNS A record, in this case, from anywhere, a DNS lookup of the guest.corp.com will get the 192.0.2.1 IP Address, this will work fine for the Guests inside your network and they will get the portal with no issues, anyone from the internet will not get any response.&lt;BR /&gt;And obviously the second option to use your local DNS server for the guests.&lt;BR /&gt;There is no DHCP option to solve the above.&lt;BR /&gt;</description>
      <pubDate>Thu, 01 Sep 2022 16:03:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/ise-2-4-and-9800-wlc-wireless-guest-issue/m-p/4679856#M245635</guid>
      <dc:creator>Grendizer</dc:creator>
      <dc:date>2022-09-01T16:03:05Z</dc:date>
    </item>
  </channel>
</rss>

