<?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 In my case the users are all in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901108#M40056</link>
    <description>&lt;P&gt;In my case the users are all within the Local ACS database. AD is not being used.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Mar 2016 19:29:28 GMT</pubDate>
    <dc:creator>bnace</dc:creator>
    <dc:date>2016-03-09T19:29:28Z</dc:date>
    <item>
      <title>ACS Time Sync for User Authentication</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901106#M40054</link>
      <description>&lt;P&gt;I have a WLC that has two identical ACS 5.5 used as RADIUS for authentication. The primary works fine without any issues. The secondary (relative to the WLC) is having authentication issues. There is no path issue between the WLC and the two ACSs. I do see that the secondary has not kept synchronization with the NTP clock. I see documents where this can be an issue with machine authentication but none that address user authentication. Can anyone provide information about whether this can be an issue and the documentation to support. Users are using PEAP (no certificate) to authenticate. The time difference is ~ 4 minutes in drift at this time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:33:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901106#M40054</guid>
      <dc:creator>bnace</dc:creator>
      <dc:date>2019-03-11T06:33:37Z</dc:date>
    </item>
    <item>
      <title>If ACS is configured to use</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901107#M40055</link>
      <description>&lt;P&gt;If ACS is configured to use AD as the back-end user database, the maximum clock drift allowed is five minutes. This would affect both machine and user authentications.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What reason is ACS giving to reject the authentication attempts?&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Javier Henderson&lt;/P&gt;
&lt;P&gt;Cisco Systems&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 19:14:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901107#M40055</guid>
      <dc:creator>Javier Henderson</dc:creator>
      <dc:date>2016-03-09T19:14:38Z</dc:date>
    </item>
    <item>
      <title>In my case the users are all</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901108#M40056</link>
      <description>&lt;P&gt;In my case the users are all within the Local ACS database. AD is not being used.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 19:29:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-time-sync-for-user-authentication/m-p/2901108#M40056</guid>
      <dc:creator>bnace</dc:creator>
      <dc:date>2016-03-09T19:29:28Z</dc:date>
    </item>
  </channel>
</rss>

