<?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 Re: Creating multiple Access Policies in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/creating-multiple-access-policies/m-p/1828795#M241650</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think my issue reside somewhere in here - specifically in the &lt;/P&gt;&lt;H2&gt;Service Selection Policy section&lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259"&gt;&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259"&gt;http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS comes preconfigured with two default access&amp;nbsp; services: Default Device Admin and Default Network Access. The&amp;nbsp; rules-based service selection mode is configured to use the AAA protocol&amp;nbsp; as the selection criterion and hence when a TACACS+ request comes in,&amp;nbsp; the Default Device Admin service is used and &lt;STRONG&gt;when a RADIUS request comes&amp;nbsp; in&lt;/STRONG&gt;, the Default Network Access service is used. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I am looking for is a way to have the radius request be smart enough to see if it is a Host authentication or an LDAP request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when looking at the service selection policy rule creation, there are only 2 match criteria tacacs+ and radius.&lt;/P&gt;&lt;P&gt;and radius will point to the Default Network Access, which I currently have pointing to the LDAP store. which does not contain the Mac Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have figured out a work around&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under users and Identity stores&lt;/P&gt;&lt;P&gt;I create Identity store sequences&lt;/P&gt;&lt;P&gt;and add LDAP and internal hosts to the ISS&lt;/P&gt;&lt;P&gt;then under the access policy I change the default network access to point to the ISS instead of the LDAP store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This allows the local mac database and the LDAP store to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wondering if there is a more efficient way or if I can separate the two.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 28 Nov 2011 02:40:44 GMT</pubDate>
    <dc:creator>Andrew MacTaggart</dc:creator>
    <dc:date>2011-11-28T02:40:44Z</dc:date>
    <item>
      <title>Creating multiple Access Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/creating-multiple-access-policies/m-p/1828794#M241628</link>
      <description>&lt;P&gt;Greetings&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have set up an LDAP indentity store that provides WLC wlan authentication&amp;nbsp; - this works well - points to the default network access&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have created a host Identity&amp;nbsp; in the host local store.&lt;/P&gt;&lt;P&gt;I have created policy elements based on time&lt;/P&gt;&lt;P&gt;I created a new Access Policies&amp;nbsp; that match to radius and points to the Internal Hosts store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;would like to have both running at same time, each policy and datastore providing authentication for&amp;nbsp; separate WLANs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am following this document for MAC authentication&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008084f13b.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk722/tk809/technologies_configuration_example09186a008084f13b.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using acs 5.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try to authenticate with the MAC address, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I get error 22056 Subject not found in the applicable identity store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The log shows that the Username {mac address} is pointing to the LDAP authentication under the Default Network Access policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So it seems like the ACS is only looking at the default network access policy and ignoring the MAC Filter Policy I created.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steps I followed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Assume LDAP store is&amp;nbsp; configured for the &lt;/P&gt;&lt;P&gt;Default Network Access policy&lt;/P&gt;&lt;P&gt;Is up and running&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I creat a host in the Internal Identity Store populate all required fields&lt;/P&gt;&lt;P&gt;under Policy elements I create &lt;/P&gt;&lt;P&gt;a session condition based on time&lt;/P&gt;&lt;P&gt;and a Authorization and permissions element under network access&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under Access policies&lt;/P&gt;&lt;P&gt;I create a new access policy - mark allowed protocols&lt;/P&gt;&lt;P&gt;and enable it under Service Selection rules &amp;gt; match to radius = same as the LDAP&lt;/P&gt;&lt;P&gt;got a green light&lt;/P&gt;&lt;P&gt;under the identity&amp;nbsp; I point to internal Hosts&lt;/P&gt;&lt;P&gt;under authorization I create a new policy and point to my time element and my Authorization Profile&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;on WLC&lt;/P&gt;&lt;P&gt;create wlan&lt;/P&gt;&lt;P&gt;security none - for now&lt;/P&gt;&lt;P&gt;layer 2 - clicked mac filtering&lt;/P&gt;&lt;P&gt;aaa servers pointing to ACS server created under the security tab.&lt;/P&gt;&lt;P&gt;under security tab click mac filtering&lt;/P&gt;&lt;P&gt;select cisco acs and : delimiter, but have tried hyphon as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I look at the acs logs&lt;/P&gt;&lt;P&gt;get radius fail status&lt;/P&gt;&lt;P&gt;username is the mac address of my machine&lt;/P&gt;&lt;P&gt;Access Service pointing to Default Network Access&lt;/P&gt;&lt;P&gt;auth method Lookup - I do have under the protocols allowed section of the access policy lookup checked.&lt;/P&gt;&lt;P&gt;Failure reason&lt;/P&gt;&lt;P&gt;22056&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts on where to pin point the issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 01:35:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/creating-multiple-access-policies/m-p/1828794#M241628</guid>
      <dc:creator>Andrew MacTaggart</dc:creator>
      <dc:date>2019-03-11T01:35:01Z</dc:date>
    </item>
    <item>
      <title>Re: Creating multiple Access Policies</title>
      <link>https://community.cisco.com/t5/network-access-control/creating-multiple-access-policies/m-p/1828795#M241650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think my issue reside somewhere in here - specifically in the &lt;/P&gt;&lt;H2&gt;Service Selection Policy section&lt;/H2&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259"&gt;&lt;BR /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259"&gt;http://www.cisco.com/en/US/docs/net_mgmt/cisco_secure_access_control_system/5.2/user/guide/policy_mod.html#wp1074259&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACS comes preconfigured with two default access&amp;nbsp; services: Default Device Admin and Default Network Access. The&amp;nbsp; rules-based service selection mode is configured to use the AAA protocol&amp;nbsp; as the selection criterion and hence when a TACACS+ request comes in,&amp;nbsp; the Default Device Admin service is used and &lt;STRONG&gt;when a RADIUS request comes&amp;nbsp; in&lt;/STRONG&gt;, the Default Network Access service is used. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what I am looking for is a way to have the radius request be smart enough to see if it is a Host authentication or an LDAP request.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when looking at the service selection policy rule creation, there are only 2 match criteria tacacs+ and radius.&lt;/P&gt;&lt;P&gt;and radius will point to the Default Network Access, which I currently have pointing to the LDAP store. which does not contain the Mac Address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have figured out a work around&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under users and Identity stores&lt;/P&gt;&lt;P&gt;I create Identity store sequences&lt;/P&gt;&lt;P&gt;and add LDAP and internal hosts to the ISS&lt;/P&gt;&lt;P&gt;then under the access policy I change the default network access to point to the ISS instead of the LDAP store.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This allows the local mac database and the LDAP store to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Wondering if there is a more efficient way or if I can separate the two.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 28 Nov 2011 02:40:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/creating-multiple-access-policies/m-p/1828795#M241650</guid>
      <dc:creator>Andrew MacTaggart</dc:creator>
      <dc:date>2011-11-28T02:40:44Z</dc:date>
    </item>
  </channel>
</rss>

