<?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 Flexconnect standalone mode EAP-FASTv2 in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/flexconnect-standalone-mode-eap-fastv2/m-p/4075157#M10493</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm aware that the network access device is irrelevant to the EAP methods used as it encapsulated in RADIUS. We intend to deploy a wireless setup where APs in the branch should be able to authenticate users in the event of a WAN failure using the local ISE PSN. The APs are configured in flexconnect mode and in the normal operational scenario would be doing local switching, central authentication. In a WAN failure scenario the expectation is for it to perform local switching, local authentication in standalone mode.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For authentication we intend to use EAP-FASTv2 with EAP-chaining. Would like to know if anyone has encountered any limitations in this type of configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aadhil&lt;/P&gt;</description>
    <pubDate>Mon, 05 Jul 2021 18:59:15 GMT</pubDate>
    <dc:creator>m.abdulmajeed</dc:creator>
    <dc:date>2021-07-05T18:59:15Z</dc:date>
    <item>
      <title>Flexconnect standalone mode EAP-FASTv2</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-standalone-mode-eap-fastv2/m-p/4075157#M10493</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I'm aware that the network access device is irrelevant to the EAP methods used as it encapsulated in RADIUS. We intend to deploy a wireless setup where APs in the branch should be able to authenticate users in the event of a WAN failure using the local ISE PSN. The APs are configured in flexconnect mode and in the normal operational scenario would be doing local switching, central authentication. In a WAN failure scenario the expectation is for it to perform local switching, local authentication in standalone mode.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For authentication we intend to use EAP-FASTv2 with EAP-chaining. Would like to know if anyone has encountered any limitations in this type of configuration.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aadhil&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 18:59:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-standalone-mode-eap-fastv2/m-p/4075157#M10493</guid>
      <dc:creator>m.abdulmajeed</dc:creator>
      <dc:date>2021-07-05T18:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Flexconnect standalone mode EAP-FASTv2</title>
      <link>https://community.cisco.com/t5/wireless/flexconnect-standalone-mode-eap-fastv2/m-p/4086049#M10494</link>
      <description>&lt;P&gt;Before implement check whether do you have certificate in ISE.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Please rate if this post helpful for you&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 14 May 2020 18:18:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/flexconnect-standalone-mode-eap-fastv2/m-p/4086049#M10494</guid>
      <dc:creator>Shivu b</dc:creator>
      <dc:date>2020-05-14T18:18:26Z</dc:date>
    </item>
  </channel>
</rss>

