<?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 Guest and Sponsor Portal Issue in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721137#M578237</link>
    <description>But your clients won’t trust a self-signed certificate. If you are using a public certificate for admin, you should get a new certificate and add the sponsor URL as SAN entry. Same if you are using a private CA.&lt;BR /&gt;</description>
    <pubDate>Mon, 14 Nov 2022 15:50:19 GMT</pubDate>
    <dc:creator>ahollifield</dc:creator>
    <dc:date>2022-11-14T15:50:19Z</dc:date>
    <item>
      <title>ISE 2.4 Guest and Sponsor Portal Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4720975#M578225</link>
      <description>&lt;P&gt;Hi Guys,&lt;/P&gt;
&lt;P&gt;I have a customer who is wanting to setup Guest and Sponsor Portals on their ISE (2.4 Patch 8).&amp;nbsp; &amp;nbsp;Both portals are configured to use the same Certificate Group Tag, the certificate is signed by Entrust and configured for Portal usage.&amp;nbsp; &amp;nbsp;&lt;/P&gt;
&lt;P&gt;The guest portal is configured to use port 8443 on Gig 2&lt;/P&gt;
&lt;P&gt;The sponsor portal is configured to use port 8443 on Gig 0 and using a FQDN (Internal DNS servers have been updated to resolve the ISE ip)&lt;/P&gt;
&lt;P&gt;When a wireless client accesses the guest portal, everything works fine.&amp;nbsp; However, when a client accesses the sponsor portal from the internal network, the ISE is presenting its admin certificate rather than the Entrust one.&amp;nbsp; As such the client receives a certificate warning&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Its as if the ISE is ignoring the certificate group tag that its been configured with.&lt;/P&gt;
&lt;P&gt;Any idea on how to resolve this issue please?&lt;/P&gt;
&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Scott&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2022 11:49:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4720975#M578225</guid>
      <dc:creator>scottbreslin</dc:creator>
      <dc:date>2022-11-14T11:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Guest and Sponsor Portal Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721077#M578230</link>
      <description>&lt;P&gt;Yup really common issue on ISE.&amp;nbsp; I usually put the sponsor portal URL as a SAN name in the admin certificate since ISE does a very strange redirection to the sponsor portal.&amp;nbsp; It connects to standard HTTPS/443 first which uses the admin certificate.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-743964.html" target="_blank"&gt;https://www.cisco.com/c/en/us/products/collateral/security/identity-services-engine/bulletin-c25-743964.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2022 14:10:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721077#M578230</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-11-14T14:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Guest and Sponsor Portal Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721129#M578236</link>
      <description>&lt;P&gt;Thanks for the reply.&lt;/P&gt;
&lt;P&gt;So based on what you have said, I can create a self signed certificate, add the FQDN of the sponsor portal into the SAN and tick the admin usage box.&amp;nbsp; Do i also need to tick the portal usage box?&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2022 15:29:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721129#M578236</guid>
      <dc:creator>scottbreslin</dc:creator>
      <dc:date>2022-11-14T15:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Guest and Sponsor Portal Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721137#M578237</link>
      <description>But your clients won’t trust a self-signed certificate. If you are using a public certificate for admin, you should get a new certificate and add the sponsor URL as SAN entry. Same if you are using a private CA.&lt;BR /&gt;</description>
      <pubDate>Mon, 14 Nov 2022 15:50:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721137#M578237</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2022-11-14T15:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Guest and Sponsor Portal Issue</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721147#M578238</link>
      <description>&lt;P&gt;Yes the admin portal is currently using a cert signed by their private CA&lt;/P&gt;</description>
      <pubDate>Mon, 14 Nov 2022 16:08:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-guest-and-sponsor-portal-issue/m-p/4721147#M578238</guid>
      <dc:creator>scottbreslin</dc:creator>
      <dc:date>2022-11-14T16:08:58Z</dc:date>
    </item>
  </channel>
</rss>

