<?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 authorization policy in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-5-2-authorization-policy/m-p/1998199#M186249</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes ths is possible, the ssid is carried in the called station id which is an av pair sent in the access-request. The format of the called-station-id is &lt;SSID&gt;, so you can build your authorization policy with a compound condition of "called-station-id ends with ssid" then you can combine this with the AD1:ExternalGroups and set the permit-access or deny-access result depending on your implementation. Also the ssid is case sensitive when acs makes its decision so keep that in mind.&lt;/SSID&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at the authentication report in ACS you can see the ssid that I am referring to in the called-station id in the logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Aug 2012 10:36:26 GMT</pubDate>
    <dc:creator>Tarik Admani</dc:creator>
    <dc:date>2012-08-07T10:36:26Z</dc:date>
    <item>
      <title>ACS 5.2 authorization policy</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-authorization-policy/m-p/1998198#M186229</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;is there any method to control an access to the different WLAN(PEAP) on the same ACS 5.2 and WLC?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is, there is two AD groups the one have access to domain network only the other group have access to internet only &lt;BR /&gt;and may be third group that have access to both networks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Currently if i add new authorization policy the user will have access to both networks... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many thanks, in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 02:23:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-authorization-policy/m-p/1998198#M186229</guid>
      <dc:creator>Anatoly Fedchik</dc:creator>
      <dc:date>2019-03-11T02:23:39Z</dc:date>
    </item>
    <item>
      <title>ACS 5.2 authorization policy</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-5-2-authorization-policy/m-p/1998199#M186249</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes ths is possible, the ssid is carried in the called station id which is an av pair sent in the access-request. The format of the called-station-id is &lt;SSID&gt;, so you can build your authorization policy with a compound condition of "called-station-id ends with ssid" then you can combine this with the AD1:ExternalGroups and set the permit-access or deny-access result depending on your implementation. Also the ssid is case sensitive when acs makes its decision so keep that in mind.&lt;/SSID&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you look at the authentication report in ACS you can see the ssid that I am referring to in the called-station id in the logs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tarik Admani &lt;BR /&gt;*Please rate helpful posts*&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2012 10:36:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-5-2-authorization-policy/m-p/1998199#M186249</guid>
      <dc:creator>Tarik Admani</dc:creator>
      <dc:date>2012-08-07T10:36:26Z</dc:date>
    </item>
  </channel>
</rss>

