<?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 CWA URL Redirection for https in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426842#M511604</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Matias, however I should have mentioned this is CWA on a switch wired network, not WLC.&amp;nbsp; I have the following ip http and ACL configured:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip http server&lt;/P&gt;&lt;P&gt;ip http secure-server&lt;/P&gt;&lt;P&gt;ip http secure-active-session-modules none&lt;/P&gt;&lt;P&gt;ip http active-session-modules none&lt;/P&gt;&lt;P&gt;ip access-list extended ACL_WEBAUTH_REDIRECT&lt;/P&gt;&lt;P&gt; permit tcp any any eq www&lt;/P&gt;&lt;P&gt; permit tcp any any eq 443&lt;/P&gt;&lt;P&gt; deny ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Mar 2018 12:31:48 GMT</pubDate>
    <dc:creator>tolarosa@cisco.com</dc:creator>
    <dc:date>2018-03-14T12:31:48Z</dc:date>
    <item>
      <title>ISE CWA URL Redirection for https</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426840#M511600</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm running into some issues with CWA URL Redirection to work with https sessions.&amp;nbsp; We try to browse to a https websites (google, etc) and CWA URL Redirection doesn't work.&amp;nbsp; Works great with http websites. Is there a workaround or a solution for this type of situation?&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;-Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2018 18:55:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426840#M511600</guid>
      <dc:creator>tolarosa@cisco.com</dc:creator>
      <dc:date>2018-03-13T18:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: ISE CWA URL Redirection for https</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426841#M511602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Hi Tony. &lt;/SPAN&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;You have to enable it: &lt;/SPAN&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;"config network web-auth https-redirect enable"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;In these links, you will find the full information.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://supportforums.cisco.com/t5/wireless-mobility-documents/understanding-https-redirect-over-web-auth/ta-p/3143359" title="https://supportforums.cisco.com/t5/wireless-mobility-documents/understanding-https-redirect-over-web-auth/ta-p/3143359"&gt;Understanding HTTPS Redirect over Web-a... - Cisco Support Community&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/118826-config-https-webauth-00.html" title="https://www.cisco.com/c/en/us/support/docs/wireless-mobility/wireless-lan-wlan/118826-config-https-webauth-00.html"&gt;Configure HTTPS Redirect over Web-auth - Cisco&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;I hope you find it useful.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Regards.-&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 13 Mar 2018 21:33:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426841#M511602</guid>
      <dc:creator>#Mat</dc:creator>
      <dc:date>2018-03-13T21:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE CWA URL Redirection for https</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426842#M511604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Matias, however I should have mentioned this is CWA on a switch wired network, not WLC.&amp;nbsp; I have the following ip http and ACL configured:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ip http server&lt;/P&gt;&lt;P&gt;ip http secure-server&lt;/P&gt;&lt;P&gt;ip http secure-active-session-modules none&lt;/P&gt;&lt;P&gt;ip http active-session-modules none&lt;/P&gt;&lt;P&gt;ip access-list extended ACL_WEBAUTH_REDIRECT&lt;/P&gt;&lt;P&gt; permit tcp any any eq www&lt;/P&gt;&lt;P&gt; permit tcp any any eq 443&lt;/P&gt;&lt;P&gt; deny ip any any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Tony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Mar 2018 12:31:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426842#M511604</guid>
      <dc:creator>tolarosa@cisco.com</dc:creator>
      <dc:date>2018-03-14T12:31:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE CWA URL Redirection for https</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426843#M511606</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Likely issue is that the client browser is not trusting the cert from switch.&amp;nbsp; In the process of redirection, then switch must respond directly to the HTTPS request and attempt redirect.&amp;nbsp; Since the certificate does not match expected for target site, such as Google.com, the browser will likely produce an error.&amp;nbsp; Depending on browser version and config, it may simply allow you to continue, but as browsers lock down untrusted content, it may not allow user to proceed at all.&amp;nbsp; Some mobile clients handle captive portals by sending out discovery packets on http to auto-open a mini-browser for auth.&amp;nbsp; On wired, you will likely not see this yet.&amp;nbsp; Although not ideal, one option is to have users set their home page to company's internal landing page, or to have guests/contractors open page to the internal company page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Mar 2018 13:15:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426843#M511606</guid>
      <dc:creator>Craig Hyps</dc:creator>
      <dc:date>2018-03-14T13:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: ISE CWA URL Redirection for https</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426844#M511608</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If you are testing with Chrome going to Google your ACL probably wouldn't work as Chrome will default to using QUIC protocol (UDP/443) and your ACL doesn't intercept that and the switch would have no chance of redirecting a proprietary protocol.&amp;nbsp; Do you have a DACL applied as well to block traffic? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am assuming you have tried other SSL web sites in browsers other than Chrome and they don't redirect either.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Mar 2018 13:43:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-cwa-url-redirection-for-https/m-p/3426844#M511608</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-03-15T13:43:10Z</dc:date>
    </item>
  </channel>
</rss>

