<?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 ACS 5.2 integration with RSA allow only one login every min in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789552#M246810</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RSA token caching is a commited feature for ACS 5.5 scheduled for FCS towards the end of this year&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 15 Feb 2013 14:34:30 GMT</pubDate>
    <dc:creator>jrabinow</dc:creator>
    <dc:date>2013-02-15T14:34:30Z</dc:date>
    <item>
      <title>ACS 5.2 integration with RSA allow only one login every min</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789548#M246806</link>
      <description>&lt;P&gt;Hello &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I have an ACS 5,2.0.26-8 running on VM intergrated with RSA. Users are able to login using their RSA passcode for network management utilizing TACACS. The problem seam to be related with RSA token caching. Once a user login sucessful on device A using current token he can not login with the same token on another device. User must wait for a new token and then he can login again.&amp;nbsp; &lt;/P&gt;&lt;P&gt;Before moving to ACS 5.2 we were using ACS 4.2 (intergrated with the same RSA) and back then ACS 4.2 cache passcode so user where able to login on devices using the same passcode. When the token change user have to use the new one.&amp;nbsp; &lt;/P&gt;&lt;P&gt;Does anyone know a way to overcome this problem providing the same functionality like the "Token Card Settings" Durantion option under group properties, to cache token for a specific period. The global option for caching under RSA definition on 5.2 does not solve the problem. (make on difference)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;DIV class="mcePaste" id="_mcePaste" style="position: absolute; width: 1px; height: 1px; overflow: hidden; top: 0px; left: -10000px;"&gt;﻿&lt;/DIV&gt;</description>
      <pubDate>Mon, 11 Mar 2019 01:31:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789548#M246806</guid>
      <dc:creator>haris_drimouras</dc:creator>
      <dc:date>2019-03-11T01:31:23Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 integration with RSA allow only one login every min</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789549#M246807</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Did you get this resolved or it is still same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Aijaz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2013 13:31:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789549#M246807</guid>
      <dc:creator>aijazbeigh</dc:creator>
      <dc:date>2013-02-15T13:31:24Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 integration with RSA allow only one login every min</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789550#M246808</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This problem still remains. Using ACS 5.2 each RSA token can only be used once. This outcome is from our experience and testing&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Haris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2013 13:48:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789550#M246808</guid>
      <dc:creator>haris_drimouras</dc:creator>
      <dc:date>2013-02-15T13:48:16Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 integration with RSA allow only one login every min</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789551#M246809</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Haris,&lt;/P&gt;&lt;P&gt;Thanks for info. Did you raise any TAC case for this. Or did you had response from Cisco.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Aijaz&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2013 14:22:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789551#M246809</guid>
      <dc:creator>aijazbeigh</dc:creator>
      <dc:date>2013-02-15T14:22:51Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 integration with RSA allow only one login every min</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789552#M246810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;RSA token caching is a commited feature for ACS 5.5 scheduled for FCS towards the end of this year&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 15 Feb 2013 14:34:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-integration-with-rsa-allow-only-one-login-every-min/m-p/1789552#M246810</guid>
      <dc:creator>jrabinow</dc:creator>
      <dc:date>2013-02-15T14:34:30Z</dc:date>
    </item>
  </channel>
</rss>

