<?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 Authenticate VPN users via ACS 5 and AD via External Identity St in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175461#M118526</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, jkatyal...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had disabled my defualt network acess policy for a more granular access policy. Should I create a new end station filter, create a new service selection rule, and tie it into a new Acess policy? If so what protocol do I need to enable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MS-CHAPv2....PAP/ASCII &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Feb 2013 04:43:05 GMT</pubDate>
    <dc:creator>dan hale</dc:creator>
    <dc:date>2013-02-25T04:43:05Z</dc:date>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity Store</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175459#M118524</link>
      <description>&lt;P&gt;Hello All, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have installed ACS 5.4 and we are looking to authenticate our Anyconnect users with ACS via Active Directory. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think I have the correct commands in our ASA ( we had ACS 4 and authenticated our anyconnect users ).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also have configured ACS to use Active Directory&amp;nbsp; and installed the server side cert in ACS. I'm just uncertain how to program ACS to use the security group that I have setup in Active Directory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be much apperciated&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 03:07:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175459#M118524</guid>
      <dc:creator>dan hale</dc:creator>
      <dc:date>2019-03-11T03:07:34Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175460#M118525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Step 1 Select Users and Identity Stores &amp;gt; External Identity Stores &amp;gt; Active Directory, then click the Directory Groups tab.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 2 Click Select to see the available AD groups on the domain (and other trusted domains in the same forest). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The External User Groups dialog box appears displaying a list of AD groups in the domain, as well as other trusted domains in the same forest. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 3 Enter the AD groups ( in your case SECURITY GROUP) or select them from the list, then click OK. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Step 4 Click: Save Changes to save the configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NOTE: A custom condition for group mapping from the ExternalGroup attribute; the custom condition name is AD1:ExternalGroups &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go to the Access Policies.&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;Edit the authorization tab &amp;gt; edit the customise tab and move the AD1:ExternalGroups on the right side &amp;gt; click Ok.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create/edit the rule and select the AD group with any condition. This way only users froms security group will able to authenticate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jatin Katyal &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;- Do rate helpful posts -&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 23 Feb 2013 20:07:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175460#M118525</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2013-02-23T20:07:50Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175461#M118526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, jkatyal...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had disabled my defualt network acess policy for a more granular access policy. Should I create a new end station filter, create a new service selection rule, and tie it into a new Acess policy? If so what protocol do I need to enable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MS-CHAPv2....PAP/ASCII &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Feb 2013 04:43:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175461#M118526</guid>
      <dc:creator>dan hale</dc:creator>
      <dc:date>2013-02-25T04:43:05Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175462#M118527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;you can use the same "default network access rule", no need to disable it. By default, it uses PAP/ASCII. However, in case you want to push radius access-request as MS-CHAPv2 for VPN users then you have to issue the below listed command under the configured tunnel-group.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tunnel-group &lt;TUNNEL-GROUP-NAME&gt; general-attributes&lt;/TUNNEL-GROUP-NAME&gt;&lt;/P&gt;&lt;P&gt;password-management&lt;/P&gt;&lt;P&gt;exit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if you have any further questions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jatin Katyal &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;- Do rate helpful posts -&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Feb 2013 05:52:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175462#M118527</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2013-02-25T05:52:16Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175463#M118528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Jatin, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a specific acess policy for vpn users called "VPN-Users Network Access" and it works well if I set the end station filter and compound condition to "ANY"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It Seems that I should lock this down to be more secure for the "End Station Filter".....?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If so what should my filter be....the IP of the ASA or hostname?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 04:40:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175463#M118528</guid>
      <dc:creator>dan hale</dc:creator>
      <dc:date>2013-02-26T04:40:52Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175464#M118529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In that case you should you lock down the ASA with "device ip" attribute rather then using "end station filter" attribute and the define the ip address of the ASA. Here end station would be -- End stations that initiate and terminate connections like vpn client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;H3&gt; Policy Conditions &lt;/H3&gt;&lt;P&gt; You can define simple conditions in rule tables based on attributes in: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Customizable&amp;nbsp; conditions—You can create custom conditions based on protocol&amp;nbsp; dictionaries and identity dictionaries that ACS knows about. You define&amp;nbsp; custom conditions in a policy rule page; you cannot define them as&amp;nbsp; separate condition objects. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard&amp;nbsp; conditions—You can use standard conditions, which are based on&amp;nbsp; attributes that are always available, such as device IP address,&amp;nbsp; protocol, and username-related fields. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Jatin Katyal &lt;BR /&gt; &lt;BR /&gt; &lt;BR /&gt;- Do rate helpful posts -&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 26 Feb 2013 06:50:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175464#M118529</guid>
      <dc:creator>Jatin Katyal</dc:creator>
      <dc:date>2013-02-26T06:50:16Z</dc:date>
    </item>
    <item>
      <title>Authenticate VPN users via ACS 5 and AD via External Identity St</title>
      <link>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175465#M118530</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jatin, thats what was needed....thanks for you help, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Feb 2013 03:27:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/authenticate-vpn-users-via-acs-5-and-ad-via-external-identity/m-p/2175465#M118530</guid>
      <dc:creator>dan hale</dc:creator>
      <dc:date>2013-02-27T03:27:45Z</dc:date>
    </item>
  </channel>
</rss>

