<?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: ISE 2.4 Authorization policy exceptions in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3703186#M507787</link>
    <description>&lt;P&gt;Thanks Paul for the solution. Once I created the new conditions in the global exceptions on the default policy set users now have access to our EPNM servers. &lt;/P&gt;</description>
    <pubDate>Fri, 07 Sep 2018 21:47:48 GMT</pubDate>
    <dc:creator>ssokolic</dc:creator>
    <dc:date>2018-09-07T21:47:48Z</dc:date>
    <item>
      <title>ISE 2.4 Authorization policy exceptions</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3702187#M507785</link>
      <description>&lt;P&gt;I deployed a 2.4 ISE .ova in our customers test lab. It's used as our EPNM Radius server. I've created the LDAP external identity source successfully along with authorization profiles. Like I did in ISE 1.4. Now I'm trying to set up Authorization Policy exceptions.&amp;nbsp; The Policy UI in 2.4 is much different from the 1.4 UI. In our 1.4 ISE I was able to define authorization policy exceptions like the attached&amp;nbsp; ISE 1.4 screenshot shows with conditions based on the created LDAP groups.&amp;nbsp; But in 2.4 I'm confused on where I would do this. In the attached ISE 2.4 screenshot I see local exceptions and global exceptions as shown on the default policy. Is this where I would define these exceptions? What would be the difference between local vs. global in this case? If I try to define exceptions like they were defined in the ISE 1.4 instance I don't have any selections containing our defined LDAP groups. My apologies as I'm not a security nor ISE expert by any means. Any help would be greatly appreciated.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 15:17:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3702187#M507785</guid>
      <dc:creator>ssokolic</dc:creator>
      <dc:date>2018-09-06T15:17:58Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Authorization policy exceptions</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3702348#M507786</link>
      <description>&lt;P&gt;In your 1.4 ISE environment you haven't enabled policy sets which is why the GUI looks different.&amp;nbsp; Policy Sets have been around since 1.2, but they were disabled by default.&amp;nbsp; To mimic the screen shot you want to use the Global Exception.&amp;nbsp; Once you add a line to the Global Exception it will appear in all your policy sets.&amp;nbsp; The Local Exceptions are only applied to the policy set your are in.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 17:43:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3702348#M507786</guid>
      <dc:creator>paul</dc:creator>
      <dc:date>2018-09-06T17:43:38Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Authorization policy exceptions</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3703186#M507787</link>
      <description>&lt;P&gt;Thanks Paul for the solution. Once I created the new conditions in the global exceptions on the default policy set users now have access to our EPNM servers. &lt;/P&gt;</description>
      <pubDate>Fri, 07 Sep 2018 21:47:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authorization-policy-exceptions/m-p/3703186#M507787</guid>
      <dc:creator>ssokolic</dc:creator>
      <dc:date>2018-09-07T21:47:48Z</dc:date>
    </item>
  </channel>
</rss>

