<?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 Critical Authentication event - reinitialize all sessions in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3679085#M25316</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;I'm working on a ISE/Trustsec deployment for wired devices using ibns 2.0. The dev environment is working well:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Clients authenticate successfully and are dynamically assigned SGTs from ISE&lt;/LI&gt;
&lt;LI&gt;Switches download CTS environment data from ISE (SGTs and SGACLs) and ISE policy is enforced correctly.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm now looking at how to handle a critical authentication event where ISE becomes unavailable:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Unauthenticated clients are authorised ok by the switch's ibns 2.0 identity control policy. SGTs are applied statically though VLAN membership&lt;/LI&gt;
&lt;LI&gt;CTS environment data (SGTs and SGACLs) learned from ISE eventually times out (ISE default for this timeout is 24 hours).&lt;/LI&gt;
&lt;LI&gt;Clients that authenticated successfully (before RADIUS became unavailable) remain authorised with their dynamically assigned SGT. Periodic authentication isn't enabled so clients remain authorised until the session ends.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The problem I'm seeing is that if ISE is unavailable for long enough and the switch's CTS environmental data times out, then the switch loses the SGACLs/SGTs required to enforce policy for the ISE authenticated devices with their dynamically assigned SGTs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I thought the old legacy 802.1x command "&lt;STRONG&gt;authentication event server dead action reinitialize vlan X&lt;/STRONG&gt;" might help reinitialize authenticated clients when a critical authentication event occurs but the bug CSCul89568 (and my testing) shows that this is only possible if periodic authentication is enabled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I created a simple EEM script below which clears all authenticated sessions when RADIUS becomes unavailable. Clients are then authorised by the switch with statically assigned SGTs (enforcement is done through static SGACLs).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;event manager applet CRITICAL-CLEAR-SESSIONS&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; event syslog pattern "RADIUS-4-RADIUS_DEAD" maxrun 5&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; action 1.0 cli command "enable"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; action 1.1 cli command "clear access-session"&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone suggest a better way of dealing with this kind of event? I could increase the cts environmental data timeout or enable periodic authentication.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;Andy&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 08:47:36 GMT</pubDate>
    <dc:creator>andrewswanson</dc:creator>
    <dc:date>2019-03-11T08:47:36Z</dc:date>
    <item>
      <title>Critical Authentication event - reinitialize all sessions</title>
      <link>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3679085#M25316</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;I'm working on a ISE/Trustsec deployment for wired devices using ibns 2.0. The dev environment is working well:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Clients authenticate successfully and are dynamically assigned SGTs from ISE&lt;/LI&gt;
&lt;LI&gt;Switches download CTS environment data from ISE (SGTs and SGACLs) and ISE policy is enforced correctly.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm now looking at how to handle a critical authentication event where ISE becomes unavailable:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Unauthenticated clients are authorised ok by the switch's ibns 2.0 identity control policy. SGTs are applied statically though VLAN membership&lt;/LI&gt;
&lt;LI&gt;CTS environment data (SGTs and SGACLs) learned from ISE eventually times out (ISE default for this timeout is 24 hours).&lt;/LI&gt;
&lt;LI&gt;Clients that authenticated successfully (before RADIUS became unavailable) remain authorised with their dynamically assigned SGT. Periodic authentication isn't enabled so clients remain authorised until the session ends.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;The problem I'm seeing is that if ISE is unavailable for long enough and the switch's CTS environmental data times out, then the switch loses the SGACLs/SGTs required to enforce policy for the ISE authenticated devices with their dynamically assigned SGTs.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I thought the old legacy 802.1x command "&lt;STRONG&gt;authentication event server dead action reinitialize vlan X&lt;/STRONG&gt;" might help reinitialize authenticated clients when a critical authentication event occurs but the bug CSCul89568 (and my testing) shows that this is only possible if periodic authentication is enabled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I created a simple EEM script below which clears all authenticated sessions when RADIUS becomes unavailable. Clients are then authorised by the switch with statically assigned SGTs (enforcement is done through static SGACLs).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;event manager applet CRITICAL-CLEAR-SESSIONS&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; event syslog pattern "RADIUS-4-RADIUS_DEAD" maxrun 5&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; action 1.0 cli command "enable"&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt; action 1.1 cli command "clear access-session"&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Can anyone suggest a better way of dealing with this kind of event? I could increase the cts environmental data timeout or enable periodic authentication.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks&lt;BR /&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 08:47:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3679085#M25316</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2019-03-11T08:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: Critical Authentication event - reinitialize all sessions</title>
      <link>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3832009#M25317</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;have you tried enabling cts cache to store the environment data and SGACL into flash. This way the last entry into cache before ISE dies will be used.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2019 08:01:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3832009#M25317</guid>
      <dc:creator>david.2018</dc:creator>
      <dc:date>2019-04-04T08:01:45Z</dc:date>
    </item>
    <item>
      <title>Re: Critical Authentication event - reinitialize all sessions</title>
      <link>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3832061#M25318</link>
      <description>&lt;P&gt;Hi David&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Thanks for the response. CTS cache isn't supported on Catalyst 3ks so that wasn't an option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Currently, I have periodic authentication enabled for all clients - during a Critical Authentication event, all clients are re-authenticated before the cts environment data times out.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Thu, 04 Apr 2019 08:59:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/critical-authentication-event-reinitialize-all-sessions/m-p/3832061#M25318</guid>
      <dc:creator>andrewswanson</dc:creator>
      <dc:date>2019-04-04T08:59:22Z</dc:date>
    </item>
  </channel>
</rss>

