<?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 Wired WebAuth support in SDA fabric in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/wired-webauth-support-in-sda-fabric/m-p/3954787#M340</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know that ISE and Cat 9000 switches do support multiple authentication fallback configuration, including WebAuth.&lt;/P&gt;
&lt;P&gt;I would like to confirm if wired WebAuth based on ISE DB (eg. wired guest access) is supported in a SDA fabric, and in detail:&lt;/P&gt;
&lt;P&gt;1) Can you configure on a wired switch port in a SDA fabric a 3-steps fallback auth method chain such as: 802.1x, then MAB, then WebAuth?&lt;/P&gt;
&lt;P&gt;2) Is this fully supported by BU and TAC? Any caveats?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thank you,&lt;/P&gt;
&lt;P&gt;Luca&lt;/P&gt;</description>
    <pubDate>Thu, 07 Nov 2019 14:19:30 GMT</pubDate>
    <dc:creator>lulironi</dc:creator>
    <dc:date>2019-11-07T14:19:30Z</dc:date>
    <item>
      <title>Wired WebAuth support in SDA fabric</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/wired-webauth-support-in-sda-fabric/m-p/3954787#M340</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know that ISE and Cat 9000 switches do support multiple authentication fallback configuration, including WebAuth.&lt;/P&gt;
&lt;P&gt;I would like to confirm if wired WebAuth based on ISE DB (eg. wired guest access) is supported in a SDA fabric, and in detail:&lt;/P&gt;
&lt;P&gt;1) Can you configure on a wired switch port in a SDA fabric a 3-steps fallback auth method chain such as: 802.1x, then MAB, then WebAuth?&lt;/P&gt;
&lt;P&gt;2) Is this fully supported by BU and TAC? Any caveats?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;thank you,&lt;/P&gt;
&lt;P&gt;Luca&lt;/P&gt;</description>
      <pubDate>Thu, 07 Nov 2019 14:19:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/wired-webauth-support-in-sda-fabric/m-p/3954787#M340</guid>
      <dc:creator>lulironi</dc:creator>
      <dc:date>2019-11-07T14:19:30Z</dc:date>
    </item>
    <item>
      <title>Re: Wired WebAuth support in SDA fabric</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/wired-webauth-support-in-sda-fabric/m-p/3955752#M347</link>
      <description>AKAIK you can use WebAuth. The caveat is as of the latest DNAC version 1.3.1.3 engineers cannot create their own authentication template under Design-&amp;gt;Authentication Template. The issue here is that the default Cisco templates deploy IBNS service templates with pre-defined configs to your edge nodes within your fabric. The current workaround is to utilize the template editor for any things you wish to modify. I am currently running an SDA fabric where we deploy the default Closed Auth template, but then tweak items via the template editor which in regard to your topic include:&lt;BR /&gt;-Modification of dot1x/mab order &amp;amp; priority&lt;BR /&gt;-Modification of the default critical auth and voice vlans&lt;BR /&gt;-8021x timers&lt;BR /&gt;-Modification of the default webauth acl&lt;BR /&gt;Via ISE I have setup the default 8021x/mab authz policy to redirect users to a guest modified hotspot portal that essentially has access to VERY little and is a generic splash page with help desk number etc. This works like a charm.</description>
      <pubDate>Fri, 08 Nov 2019 17:14:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/wired-webauth-support-in-sda-fabric/m-p/3955752#M347</guid>
      <dc:creator>Mike.Cifelli</dc:creator>
      <dc:date>2019-11-08T17:14:03Z</dc:date>
    </item>
  </channel>
</rss>

