<?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 Still continue on ISE 2.2 in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629553#M73905</link>
    <description>&lt;P&gt;Still continue on ISE 2.2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Is there any idea how to solve the problem?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Fri, 14 Apr 2017 00:21:39 GMT</pubDate>
    <dc:creator>Hasan Erhan AYDINOGLU</dc:creator>
    <dc:date>2017-04-14T00:21:39Z</dc:date>
    <item>
      <title>Cisco ISE (1.3) Posture and re-authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629549#M73901</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With posture and re-authentication, during the re-authentication the posture status swithes to pending. This results in a redirect to client provisioning and a temperorly but unwanted state with no access to network resources.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to work around this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Dennis&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:34:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629549#M73901</guid>
      <dc:creator>dennisnieuwenhuyzen</dc:creator>
      <dc:date>2019-03-11T05:34:32Z</dc:date>
    </item>
    <item>
      <title>did you ever get this figured</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629550#M73902</link>
      <description>&lt;P&gt;did you ever get this figured out? we're having the same issue.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;we have re authentication set for 3600 seconds at the authorization profile and then set the switchports for authentication periodic and to pull the timer from the server. user logs in, posturing completes and they are good for 3600 seconds. then the timer expires and the port goes back to pending but re-auth never happens. the redirect URL and the posturing ACL get reapplied to the port but the anyconnect agent never does anything and just sits there saying the endpoint is compliant. i've setup PRA on the anyconnect profile but that doesn't seem to be working either?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;so anyconnect never responds and the ports just STAY in pending and the user is forced to disconnect or reboot to get things working again.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;are posturing and re-auth mutually exclusive? what is suppposed to get the Anyconnect posturing agent to recheck the host and send to ISE?&lt;/P&gt;</description>
      <pubDate>Wed, 18 May 2016 21:23:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629550#M73902</guid>
      <dc:creator>ben.posner</dc:creator>
      <dc:date>2016-05-18T21:23:44Z</dc:date>
    </item>
    <item>
      <title>anyone? bueller? bueller?</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629551#M73903</link>
      <description>&lt;P&gt;anyone? bueller? bueller? still have the same problem on ISE 2.1. it's gotta be something i've not configured properly but i have no idea what...&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 16:04:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629551#M73903</guid>
      <dc:creator>ben.posner</dc:creator>
      <dc:date>2016-08-24T16:04:12Z</dc:date>
    </item>
    <item>
      <title>Hi Ben,</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629552#M73904</link>
      <description>&lt;P&gt;Hi Ben,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Sorry, i missed your first question. We disabled re-authentication at this customer.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Aug 2016 20:08:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629552#M73904</guid>
      <dc:creator>dennisnieuwenhuyzen</dc:creator>
      <dc:date>2016-08-24T20:08:28Z</dc:date>
    </item>
    <item>
      <title>Still continue on ISE 2.2</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629553#M73905</link>
      <description>&lt;P&gt;Still continue on ISE 2.2&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Is there any idea how to solve the problem?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 14 Apr 2017 00:21:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-posture-and-re-authentication/m-p/2629553#M73905</guid>
      <dc:creator>Hasan Erhan AYDINOGLU</dc:creator>
      <dc:date>2017-04-14T00:21:39Z</dc:date>
    </item>
  </channel>
</rss>

