<?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 ISE 2.4 Authentication - Identity Groups unavailable in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3931556#M456805</link>
    <description>&lt;P&gt;It was pointed out that our default policy set was not configured for best practice.&amp;nbsp; We had been pointing the default authentication to our RSA service.&amp;nbsp; In an attempt to change the default to deny access, I had to come up with a limiting method to prevent unnecessary/unacceptable request from being passed to the RSA service.&amp;nbsp; I thought I would use an AD group as a userid cache to qualify what userids would be sent onto the RSA service.&amp;nbsp; In addition, I am focused in the device admin section and the authentication I am handling is a tacacs communication.&amp;nbsp; As I dug into it I quickly discovered I could not manually define an AD group criteria nor could I use the previously created AD identity groups that I use in the authorization policy sets.&amp;nbsp; In fact, no identity groups are available when clicking on that icon in the authentication set.&amp;nbsp; My sad work around is this:&amp;nbsp; because we have standardized user account name, I took the tacacs username and qualified based on matching beginning characters of the usernames... While this works, that set is far greater than the userids I want to forward to our RSA service.&amp;nbsp; Is this limitation engineered by design?&amp;nbsp; Am I looking at Authentication in the wrong way?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 27 Sep 2019 15:42:13 GMT</pubDate>
    <dc:creator>ssschunk1</dc:creator>
    <dc:date>2019-09-27T15:42:13Z</dc:date>
    <item>
      <title>ISE 2.4 Authentication - Identity Groups unavailable</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3931556#M456805</link>
      <description>&lt;P&gt;It was pointed out that our default policy set was not configured for best practice.&amp;nbsp; We had been pointing the default authentication to our RSA service.&amp;nbsp; In an attempt to change the default to deny access, I had to come up with a limiting method to prevent unnecessary/unacceptable request from being passed to the RSA service.&amp;nbsp; I thought I would use an AD group as a userid cache to qualify what userids would be sent onto the RSA service.&amp;nbsp; In addition, I am focused in the device admin section and the authentication I am handling is a tacacs communication.&amp;nbsp; As I dug into it I quickly discovered I could not manually define an AD group criteria nor could I use the previously created AD identity groups that I use in the authorization policy sets.&amp;nbsp; In fact, no identity groups are available when clicking on that icon in the authentication set.&amp;nbsp; My sad work around is this:&amp;nbsp; because we have standardized user account name, I took the tacacs username and qualified based on matching beginning characters of the usernames... While this works, that set is far greater than the userids I want to forward to our RSA service.&amp;nbsp; Is this limitation engineered by design?&amp;nbsp; Am I looking at Authentication in the wrong way?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 15:42:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3931556#M456805</guid>
      <dc:creator>ssschunk1</dc:creator>
      <dc:date>2019-09-27T15:42:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Authentication - Identity Groups unavailable</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3931618#M456806</link>
      <description>&lt;P&gt;It sounds like you might be missing a step, but my bad if I misunderstood the issue. In order to have AD groups available for use within ISE policy sets, or admin access areas, you need to "add" them to ISE. &lt;BR /&gt;1. navigate to&amp;nbsp;https://&amp;lt;ISE_IP&amp;gt;/admin/#administration/administration_identitymanagement/administration_identitymanagement_external&lt;BR /&gt;2. Click on your AD connector&lt;BR /&gt;3. In the middle of the page you will have a "groups" tab, click it.&lt;BR /&gt;4. Search and add AD groups you would like to leverage within ISE.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;At this point you will have them available when you are creating radius/tacacs rules.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="ad.png" style="width: 701px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/45761iB5CBA2770C4E1506/image-dimensions/701x309?v=v2" width="701" height="309" role="button" title="ad.png" alt="ad.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2019 17:12:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3931618#M456806</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2019-09-27T17:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Authentication - Identity Groups unavailable</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3932136#M456808</link>
      <description>&lt;P&gt;You are correct on this. This is by the current design of ISE that ID groups available during authorization only but not during authentication.&lt;/P&gt;</description>
      <pubDate>Sun, 29 Sep 2019 16:52:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3932136#M456808</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-09-29T16:52:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE 2.4 Authentication - Identity Groups unavailable</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3933902#M456810</link>
      <description>Thanks. Not really the answer I wanted and it really limits my authentication options. Any insight on this becoming a future feature add?</description>
      <pubDate>Wed, 02 Oct 2019 15:41:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-2-4-authentication-identity-groups-unavailable/m-p/3933902#M456810</guid>
      <dc:creator>ssschunk1</dc:creator>
      <dc:date>2019-10-02T15:41:51Z</dc:date>
    </item>
  </channel>
</rss>

