<?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 Guest Wifi portal redirection flow in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218180#M592888</link>
    <description>&lt;P&gt;I would like to create CWA guest SSID with ISE and WLC 9800. When a client connect to the SSID, it must be redirected to guest portal automatically, which is done in my environment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Connect to SSID, then redirect to guest portal automatically. (bypass is disabled)&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Since I send the credentials to the clients via email, when they complete their registration, they must be able to leave guest portal and go to their email box. So, they must have an internet access. However, this internet access must be limited like 10 min. ---- (I tried to create ACL with deny 80, 443, then automatic redirect wouldn't work. When i created ACL with permit 80, 443, then clients wouldn't have internet access to check their emails.)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;-&amp;nbsp;&lt;SPAN&gt;The client who received the credential from his email should return to the portal and log in.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;How can i setup this flow? Would it be possible if i can do the following:&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;When the client connects, it will go to the portal with automatic redirection and register. Here, if ISE can put a sign or a flag for the radius request and 120 &lt;SPAN class=""&gt;seconds later, the session timeout occurs.&lt;/SPAN&gt; Since there is a termination-action = radius-request, if I can add the flags to the condition in the next request and redirect them to the same portal, they can log in with the credential they received.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 31 Oct 2024 15:10:58 GMT</pubDate>
    <dc:creator>omerfaruk</dc:creator>
    <dc:date>2024-10-31T15:10:58Z</dc:date>
    <item>
      <title>Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218180#M592888</link>
      <description>&lt;P&gt;I would like to create CWA guest SSID with ISE and WLC 9800. When a client connect to the SSID, it must be redirected to guest portal automatically, which is done in my environment.&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Connect to SSID, then redirect to guest portal automatically. (bypass is disabled)&lt;/P&gt;&lt;P&gt;-&amp;nbsp;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;Since I send the credentials to the clients via email, when they complete their registration, they must be able to leave guest portal and go to their email box. So, they must have an internet access. However, this internet access must be limited like 10 min. ---- (I tried to create ACL with deny 80, 443, then automatic redirect wouldn't work. When i created ACL with permit 80, 443, then clients wouldn't have internet access to check their emails.)&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;-&amp;nbsp;&lt;SPAN&gt;The client who received the credential from his email should return to the portal and log in.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;How can i setup this flow? Would it be possible if i can do the following:&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;&lt;SPAN&gt;When the client connects, it will go to the portal with automatic redirection and register. Here, if ISE can put a sign or a flag for the radius request and 120 &lt;SPAN class=""&gt;seconds later, the session timeout occurs.&lt;/SPAN&gt; Since there is a termination-action = radius-request, if I can add the flags to the condition in the next request and redirect them to the same portal, they can log in with the credential they received.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 15:10:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218180#M592888</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-10-31T15:10:58Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218207#M592890</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/1031714"&gt;@omerfaruk&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp; The ACL for redirect use deny, here one example&lt;/P&gt;
&lt;PRE&gt;ip access-list extended REDIRECT&lt;BR /&gt; deny ip any host &amp;lt;ISE-IP&amp;gt;&lt;BR /&gt; deny ip host&amp;lt;ISE-IP&amp;gt; any&lt;BR /&gt; deny udp any any eq domain&lt;BR /&gt; deny udp any eq domain any&lt;BR /&gt; permit tcp any any eq 80&lt;/PRE&gt;
&lt;P&gt;Once the client is autheticated, the ACL does not apply anymore. I recommend you to follow the guide below. Try to first make it work and then you can think how to control the access time. I am not sure what you are thinking is possible but let me take a look about possibilities&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/catalyst-9800-series-wireless-controllers/213920-central-web-authentication-cwa-on-cata.html" target="_blank"&gt;Configure Central Web Authentication (CWA) on Catalyst 9800 WLC and ISE - Cisco&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 16:06:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218207#M592890</guid>
      <dc:creator>Flavio Miranda</dc:creator>
      <dc:date>2024-10-31T16:06:07Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218216#M592891</link>
      <description>&lt;P&gt;for email I dont sure there is away to do that automatic but manually you can use sponsor instead of portal&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.netprojnetworks.com/cisco-9800-with-ise-central-web-authentication/" target="_blank"&gt;https://www.netprojnetworks.com/cisco-9800-with-ise-central-web-authentication/&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;MHM&lt;/P&gt;</description>
      <pubDate>Thu, 31 Oct 2024 16:36:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218216#M592891</guid>
      <dc:creator>MHM Cisco World</dc:creator>
      <dc:date>2024-10-31T16:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218498#M592901</link>
      <description>&lt;P&gt;I think you can workaround that by enabling the "Allow guests to log in directly from the Self-Registration Success page" in the "Self-Registration Success Settings" section. Alternatively, you can rely on the grace access feature which came with ISE 2.7, however, to leverage this feature you need to enable the guests approval in the "Registration Form Settings" section. Once the guests approval is ticked, you will see a new couple boxes showing up, one is called "Allow guests to use Grace Access during sponsor's approval". If you tick the box next to that you will see that you can set the grace time in which the guest can be connected prior to any authentication.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 09:57:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218498#M592901</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-01T09:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218580#M592910</link>
      <description>&lt;P&gt;Thanks all for quick response.&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/284594"&gt;@Aref Alsouqi&lt;/a&gt;, I have enabled the "Allow guests to log in directly from the Self-Registration Success page" option. This setting grants internet access to clients immediately after registration, which is what I needed. Now, clients can check their email inboxes right away.&lt;/P&gt;&lt;P&gt;However, after receiving their credentials from their email boxes, they should be redirected back to the portal to log in with those credentials. Could you advise on how I might configure this? If I send a Change of Authorization (CoA), will the Wi-Fi connection be briefly disconnected and reconnected, prompting the portal to reopen automatically?&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 13:11:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218580#M592910</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-01T13:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218644#M592916</link>
      <description>&lt;P&gt;The guest users will get reauthenticated next time they are about to connect to the network. For instance, if the guest user tries to reauthenticate after their session has expired they will be prompted to provide the credentials before they are allowed access to the network. I personally don't see a use case why you would want them to be kicked off the network right after they received the email with credentials and then reauthenticate! it is kinda redundant as a task. However, if you have this requirement for any specific reason then what I think you could do is setting reauthentication timer in the common tasks in the authorization profile to be something minimum, and also to set "RADIUS:Idle-Timeout" value in the "Advanced Attributes Settings" still in authorization profile. These two values/timers would trigger the guests session to be reauthenticated, so in theory it should ask them to provide their credentials before they are allowed access to the network. Keep in mind please that it is not recommended to set small timers here, I'm not sure but I think the recommendation is not go below 4 hours or something like that. But as I said, I personally think this adds complexity to the solution and probably wouldn't give a good user experience to the guest users.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Nov 2024 15:16:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5218644#M592916</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-01T15:16:29Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5220525#M593017</link>
      <description>&lt;P&gt;Thank you very much Aref.&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;Would it be possible if ISE&amp;nbsp;add a radius-attr to the WLC without affecting anything, and this attr come in the next radius request? I need to differentiate 2 radius request.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2024 16:42:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5220525#M593017</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-05T16:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5220566#M593020</link>
      <description>&lt;P&gt;You're welcome. I don't think that is possible because if ISE should return an attribute for a matched session that will apply to the session straightaway, it won't wait until the user/endpoint tries to reauthenticate before pushing those attributes.&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2024 18:19:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5220566#M593020</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-05T18:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5222598#M593098</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;We are using url-redirect av-pair in ISE Authorization profiles as follow. I would like to see portal id in the logs, but i couldn't. Because, WLC doesn't send it with radius request as follow. Is there a way to send portal id with radius? I am still trying to find something to differentiate the requests.&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-inline" image-alt="omerfaruk_1-1731318299989.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/233597iA636F501A60582C1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="omerfaruk_1-1731318299989.png" alt="omerfaruk_1-1731318299989.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;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="omerfaruk_0-1731318144120.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/233596i436E64A31BD6DA2B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="omerfaruk_0-1731318144120.png" alt="omerfaruk_0-1731318144120.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2024 09:47:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5222598#M593098</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-11T09:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5222624#M593099</link>
      <description>&lt;P&gt;AFAIK the session ID relates to ISE not to the WLC and you can see its reference in ISE RADIUS live logs at the very end of the page if I remember correctly.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Nov 2024 10:53:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5222624#M593099</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-11T10:53:02Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5223822#M593164</link>
      <description>&lt;P&gt;You are right, thanks.&lt;/P&gt;&lt;P&gt;ISE is currently adding registered guests to the 'Guest 24 Hours From Login' group. Would it be possible for ISE to change their group to 'Guest 4 Hours From Login' by assigning an Authorization Profile or using another method upon receiving a new RADIUS request?&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 15:34:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5223822#M593164</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-13T15:34:02Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5223836#M593166</link>
      <description>&lt;P&gt;You're welcome. You can change the guest type from the guest portal settings, however, that applies to all guests, still no difference to the first time guest and the returning guest.&lt;/P&gt;</description>
      <pubDate>Wed, 13 Nov 2024 16:10:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5223836#M593166</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-13T16:10:00Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5226299#M593258</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I added the following attributes from &lt;STRONG&gt;Context Visibility &amp;gt; Endpoints &amp;gt; Attributes&lt;/STRONG&gt;. I want to use them in an Authorization Policy condition, but they are not available for selection. How can I use them?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Portal.Name&lt;/TD&gt;&lt;TD&gt;Self-Registered Guest Portal test&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;SelectedAuthorizationProfiles&lt;/TD&gt;&lt;TD&gt;WLC_CWA_login&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;PortalUser.CreationType&lt;/TD&gt;&lt;TD&gt;Self Registration Guest&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;</description>
      <pubDate>Tue, 19 Nov 2024 12:10:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5226299#M593258</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-19T12:10:21Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5227656#M593320</link>
      <description>&lt;P&gt;Not sure if you can use those attributes in the authorization rules. Maybe&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/26555"&gt;@thomas&lt;/a&gt;&amp;nbsp;or&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/158532"&gt;@Arne Bier&lt;/a&gt;&amp;nbsp;can share some thoughts on this.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 11:26:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5227656#M593320</guid>
      <dc:creator>Aref Alsouqi</dc:creator>
      <dc:date>2024-11-22T11:26:17Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5227720#M593322</link>
      <description>&lt;P&gt;Endpoint Custom Attributes are simply another dictionary:attribute and should be available to use in any policy and authorization rule. See my webinar for how to configure them:&lt;/P&gt;
&lt;H3 id="user-endpoint-custom-attributes-2022-09-06" class="maps-to-line" style="margin-top: 0.6em; margin-bottom: 0.65em; unicode-bidi: plaintext; line-height: 1.5em; font-size: 1.1em; font-weight: bold; color: #32373f; font-family: 'Avenir Next', Avenir, Arial, sans-serif; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;" data-source-line="2148"&gt;▷&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU" href="https://youtu.be/nCD7LiX-XZU" data-from-md="" target="_blank"&gt;User &amp;amp; Endpoint Custom Attributes&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;2022-09-06&lt;/H3&gt;
&lt;P class="maps-to-line" style="margin-top: 0.6em; margin-bottom: 1.35em; unicode-bidi: plaintext; color: #32373f; font-family: 'Avenir Next', Avenir, Arial, sans-serif; font-size: 15px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: #ffffff; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;" data-source-line="2150"&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=189s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=189s" data-from-md="" target="_blank"&gt;03:09&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Endpoint Profiles, Endpoint Groups versus Custom Attributes&lt;BR /&gt;&lt;A class="" style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=301s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=301s" data-from-md="" target="_blank"&gt;05:01&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Defining User Custom Attributes for ISE Internal Users&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=370s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=370s" data-from-md="" target="_blank"&gt;06:10&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Defining Endpoint Custom Attributes and their Common Uses&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=456s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=456s" data-from-md="" target="_blank"&gt;07:36&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Creating User Custom Attributes&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=641s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=641s" data-from-md="" target="_blank"&gt;10:41&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: ISE 802.1X Policy Review, and Authentication&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=831s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=831s" data-from-md="" target="_blank"&gt;13:51&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo:&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Customize 802.1X Authorization Policy using Custom Attributes&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=920s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=920s" data-from-md="" target="_blank"&gt;15:20&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Edit User Custom Attribute and Authenticate with Custom Attribute&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1011s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1011s" data-from-md="" target="_blank"&gt;16:51&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Endpoint Custom Attributes&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1169s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1169s" data-from-md="" target="_blank"&gt;19:29&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Custom Attribute Policies for IOT Endpoints&lt;BR /&gt;&lt;A class="" style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1332s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1332s" data-from-md="" target="_blank"&gt;22:12&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Raspberry Pi Authorizations using ISE Profiling Policies&lt;BR /&gt;&lt;A style="background-color: transparent; color: #155bda;" title="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1356s" href="https://youtu.be/nCD7LiX-XZU&amp;amp;t=1356s" data-from-md="" target="_blank"&gt;22:36&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Demo: Use Context Visibility to Edit Endpoint Custom Attributes in ISE&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2024 14:29:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5227720#M593322</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2024-11-22T14:29:49Z</dc:date>
    </item>
    <item>
      <title>Re: Guest Wifi portal redirection flow</title>
      <link>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5228328#M593336</link>
      <description>&lt;P&gt;Thank you Aref.&lt;/P&gt;&lt;P&gt;Thomas,&amp;nbsp;it was an educational video with good information, thank you for your effort!&lt;/P&gt;&lt;P&gt;When I create custom attribute, ISE needs to be populated it. Which is I don't need. I want only use an attribute which is already in &lt;STRONG&gt;Context Visibility &amp;gt; Endpoints &amp;gt; Attributes --&amp;gt; Portal.Name. &lt;/STRONG&gt;Unfortunately, i am not able to add it to authorization policy. There should be, but i couldn't find. Is there any suggestion?&lt;/P&gt;&lt;P&gt;If I create a custom attribute and dynamically assign the portal.name value to this attribute, it will also reflect the name.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2024 08:58:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/guest-wifi-portal-redirection-flow/m-p/5228328#M593336</guid>
      <dc:creator>omerfaruk</dc:creator>
      <dc:date>2024-11-25T08:58:53Z</dc:date>
    </item>
  </channel>
</rss>

