<?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 - RADIUS AUTHENTICATION - Match on AD Group Membership to base Identity Source in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-radius-authentication-match-on-ad-group-membership-to-base/m-p/4015841#M454383</link>
    <description>&lt;P&gt;&lt;SPAN&gt;Is it possible to&amp;nbsp;match upon initial Authentication against an AD Group to then have a different Identity Source used? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Generally I'm only aware of it being possible to match against an AD Group AFTER a User has authenticated via an Authorization Policy. &lt;/SPAN&gt;&lt;SPAN&gt;Use Case is for VPN users, and the client wants to slowly role out changing authentication sources (AD to MFA). I've gotten the standard method I'm aware of working, which is via matching on a different Group-Policy and/or Tunnel-Group from the ASA, but they were looking for an easier method to deploy to end users. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If they can't get it to work this way, then I'll just work on modifying the AnyConnect Profile to point to the new FQDN URL and call it good, but I wanted to ask this space if they had ever tried matching against AD Group during initial Authentication Queries. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm thinking not, the more I think of it, as the endpoint/user hasn't been sent to the Identity Source which would then pull/provide those details.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2020 03:21:36 GMT</pubDate>
    <dc:creator>jason.erbe</dc:creator>
    <dc:date>2020-01-22T03:21:36Z</dc:date>
    <item>
      <title>ISE - RADIUS AUTHENTICATION - Match on AD Group Membership to base Identity Source</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-radius-authentication-match-on-ad-group-membership-to-base/m-p/4015841#M454383</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Is it possible to&amp;nbsp;match upon initial Authentication against an AD Group to then have a different Identity Source used? &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Generally I'm only aware of it being possible to match against an AD Group AFTER a User has authenticated via an Authorization Policy. &lt;/SPAN&gt;&lt;SPAN&gt;Use Case is for VPN users, and the client wants to slowly role out changing authentication sources (AD to MFA). I've gotten the standard method I'm aware of working, which is via matching on a different Group-Policy and/or Tunnel-Group from the ASA, but they were looking for an easier method to deploy to end users. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;If they can't get it to work this way, then I'll just work on modifying the AnyConnect Profile to point to the new FQDN URL and call it good, but I wanted to ask this space if they had ever tried matching against AD Group during initial Authentication Queries. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I'm thinking not, the more I think of it, as the endpoint/user hasn't been sent to the Identity Source which would then pull/provide those details.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2020 03:21:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-radius-authentication-match-on-ad-group-membership-to-base/m-p/4015841#M454383</guid>
      <dc:creator>jason.erbe</dc:creator>
      <dc:date>2020-01-22T03:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: ISE - RADIUS AUTHENTICATION - Match on AD Group Membership to base Identity Source</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-radius-authentication-match-on-ad-group-membership-to-base/m-p/4015877#M454385</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You can't use ad group in the authentication rule, only on authorization.&lt;BR /&gt;You need to differentiate using other attributes like you said.&lt;BR /&gt;</description>
      <pubDate>Wed, 22 Jan 2020 04:38:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-radius-authentication-match-on-ad-group-membership-to-base/m-p/4015877#M454385</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2020-01-22T04:38:49Z</dc:date>
    </item>
  </channel>
</rss>

