<?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: ACS using AD and LDAP in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304286#M546800</link>
    <description>Unless I am missing something you can add multiple external identity stores&lt;BR /&gt;and use UPN for authentication.&lt;BR /&gt;</description>
    <pubDate>Sun, 31 Dec 2017 08:13:48 GMT</pubDate>
    <dc:creator>Mohammed al Baqari</dc:creator>
    <dc:date>2017-12-31T08:13:48Z</dc:date>
    <item>
      <title>ACS using AD and LDAP</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304274#M546799</link>
      <description>&lt;P&gt;I'm trying to configure ACS for use across 2 domains (let's say "business.com" is one and "company.com" is the others) for logging into network devices and POTENTIALLY wireless, and need a bit of help/suggestions regarding configuration.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I know that using a trust relationship, I could just set up one of the servers as the main external AD identity store in ACS, and have it reach out to the other domain when a user from that segment is trying to login. However after speaking with my superior he does not want to establish a trust relationship across domains, which leads me to my main question: would I be able to set up one of external identity stores for AD, and have the other domain be configured as an LDAP external identity store? I know you can configure a primary and secondary LDAP server, but given that one of the domains has 2 controllers, I'd like to avoid doing that. I'm mostly just wondering if this type of configuration is even possible, or do I have to choose between an AD based or LDAP based ACS identity store configuration? Are there any pitfalls or caveats with this type of potential config?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Like stated above this is currently for network device login only, and may have wireless on-boarded at a later date. That part is yet to be determined.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 18:42:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304274#M546799</guid>
      <dc:creator>CClement</dc:creator>
      <dc:date>2020-02-21T18:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: ACS using AD and LDAP</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304286#M546800</link>
      <description>Unless I am missing something you can add multiple external identity stores&lt;BR /&gt;and use UPN for authentication.&lt;BR /&gt;</description>
      <pubDate>Sun, 31 Dec 2017 08:13:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304286#M546800</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2017-12-31T08:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: ACS using AD and LDAP</title>
      <link>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304570#M546802</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;You can join every node to different AD but 1 node can join only 1 AD.&lt;BR /&gt;Then on terms of identity store, ACS can have different identity stores like AD and LDAP and Local.&lt;BR /&gt;Then you have to create an identity store sequence in which your AD and LDAP will be member of.&lt;BR /&gt;&lt;BR /&gt;To answer your question in a simple way, yes you can combine both authentication server.&lt;BR /&gt;</description>
      <pubDate>Tue, 02 Jan 2018 00:11:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/acs-using-ad-and-ldap/m-p/3304570#M546802</guid>
      <dc:creator>Francesco Molino</dc:creator>
      <dc:date>2018-01-02T00:11:15Z</dc:date>
    </item>
  </channel>
</rss>

