<?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 user auth with token &amp; password in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-5-2-user-auth-with-token-password/m-p/1717081#M247505</link>
    <description>&lt;P&gt;I am migrating from ACS 4.2 to 5.2. In 4.2 you could assign one user to auth via Internal Database and another user to auth via Radius Token Server. I cannot find how to do this with 5.2. There is a note in the doc that states 'Identity-related attributes are not available as conditions in a service selection policy'. Does this mean that you can only choose one auth method for all users? If it is possible to have multiple methods, how am I able to accomplish this? Thanks......Darryl&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 01:14:18 GMT</pubDate>
    <dc:creator>dlin1</dc:creator>
    <dc:date>2019-03-11T01:14:18Z</dc:date>
    <item>
      <title>ACS 5.2 user auth with token &amp; password</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-user-auth-with-token-password/m-p/1717081#M247505</link>
      <description>&lt;P&gt;I am migrating from ACS 4.2 to 5.2. In 4.2 you could assign one user to auth via Internal Database and another user to auth via Radius Token Server. I cannot find how to do this with 5.2. There is a note in the doc that states 'Identity-related attributes are not available as conditions in a service selection policy'. Does this mean that you can only choose one auth method for all users? If it is possible to have multiple methods, how am I able to accomplish this? Thanks......Darryl&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 01:14:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-user-auth-with-token-password/m-p/1717081#M247505</guid>
      <dc:creator>dlin1</dc:creator>
      <dc:date>2019-03-11T01:14:18Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 user auth with token &amp; password</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-user-auth-with-token-password/m-p/1717082#M247529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Darryl,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do the same function but you can not create the users internally and point their password authentication to external servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS 5.x has a new feature which is called identity store sequences...for example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;UserA has an account that is stored locally on the ACS internal database and UserB has an account on the radius token server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can configure a identity store sequence which can either look in the Radius token server first and if the user is not found then will look for the user in the interal database. Then you can tie this sequence into your access policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if that helps,&lt;/P&gt;&lt;P&gt;Tarik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jul 2011 07:23:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-user-auth-with-token-password/m-p/1717082#M247529</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2011-07-29T07:23:48Z</dc:date>
    </item>
  </channel>
</rss>

